aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2020-02-10 11:47:09 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2020-02-10 11:47:09 -0300
commitbdd19e48a8c14e4e2a5edac7a6dc23de842ccdd6 (patch)
tree592c0b3b0909f8c3cc4a495e2745b462f6e4f0ae
parentc59b0be9885b40e1a555ece5d3d848575542ee8d (diff)
downloadpostgresql-bdd19e48a8c14e4e2a5edac7a6dc23de842ccdd6.tar.gz
postgresql-bdd19e48a8c14e4e2a5edac7a6dc23de842ccdd6.zip
Fix priv checks for ALTER <object> DEPENDS ON EXTENSION
Marking an object as dependant on an extension did not have any privilege check whatsoever; this allowed any user to mark objects as droppable by anyone able to DROP EXTENSION, which could be used to cause system-wide havoc. Disallow by checking that the calling user owns the mentioned object. (No constraints are placed on the extension.) Security: CVE-2020-1720 Reported-by: Tom Lane Discussion: 31605.1566429043@sss.pgh.pa.us
-rw-r--r--src/backend/commands/alter.c11
1 files changed, 11 insertions, 0 deletions
diff --git a/src/backend/commands/alter.c b/src/backend/commands/alter.c
index 4d443c13292..302f496b7d9 100644
--- a/src/backend/commands/alter.c
+++ b/src/backend/commands/alter.c
@@ -433,6 +433,17 @@ ExecAlterObjectDependsStmt(AlterObjectDependsStmt *stmt, ObjectAddress *refAddre
&rel, AccessExclusiveLock, false);
/*
+ * Verify that the user is entitled to run the command.
+ *
+ * We don't check any privileges on the extension, because that's not
+ * needed. The object owner is stipulating, by running this command, that
+ * the extension owner can drop the object whenever they feel like it,
+ * which is not considered a problem.
+ */
+ check_object_ownership(GetUserId(),
+ stmt->objectType, address, stmt->object, rel);
+
+ /*
* If a relation was involved, it would have been opened and locked. We
* don't need the relation here, but we'll retain the lock until commit.
*/