mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-14 22:39:16 +02:00
7b347409fa
In 9.6, we moved a number of functions over to using the GRANT system to control access instead of having hard-coded superuser checks. As it turns out, adminpack was creating another function in the catalog for one of those backend functions where the superuser check was removed, specifically pg_rotate_logfile(), but it didn't get the memo about having to REVOKE EXECUTE on the alternative-name function (pg_logfile_rotate()), meaning that in any installations with adminpack on 9.6 and higher, any user is able to run the pg_logfile_rotate() function, which then calls pg_rotate_logfile() and rotates the logfile. Fix by adding a new version of adminpack (1.1) which handles the REVOKE. As this function should have only been available to the superuser, this is a security issue, albeit a minor one. In HEAD, move the changes implemented for adminpack up to be adminpack 2.0 instead of 1.1. Security: CVE-2018-1115
23 lines
533 B
Makefile
23 lines
533 B
Makefile
# contrib/adminpack/Makefile
|
|
|
|
MODULE_big = adminpack
|
|
OBJS = adminpack.o $(WIN32RES)
|
|
PG_CPPFLAGS = -I$(libpq_srcdir)
|
|
|
|
EXTENSION = adminpack
|
|
DATA = adminpack--1.0.sql adminpack--1.0--1.1.sql adminpack--1.1--2.0.sql
|
|
PGFILEDESC = "adminpack - support functions for pgAdmin"
|
|
|
|
REGRESS = adminpack
|
|
|
|
ifdef USE_PGXS
|
|
PG_CONFIG = pg_config
|
|
PGXS := $(shell $(PG_CONFIG) --pgxs)
|
|
include $(PGXS)
|
|
else
|
|
subdir = contrib/adminpack
|
|
top_builddir = ../..
|
|
include $(top_builddir)/src/Makefile.global
|
|
include $(top_srcdir)/contrib/contrib-global.mk
|
|
endif
|