CVE-2022-2625: High severity postgresql vulnerability
A vulnerability was found in PostgreSQL. This attack requires permission to create non-temporary objects in at least one schema, the ability to lure or wait for an administrator to create or update an affected extension in that schema, and the ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites, this flaw allows an attacker to run arbitrary code as the victim role, which may be a superuser.
Other sources
Extension scripts replace objects not belonging to the extension.
Some extensions use CREATE OR REPLACE or CREATE IF NOT EXISTS commands. Some don't adhere to the documented rule to target only objects known to be extension members already. An attack requires permission to create non-temporary objects in at least one schema, ability to lure or wait for an administrator to create or update an affected extension in that schema, and ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites, the attacker can run arbitrary code as the victim role, which may be a superuser. Known-affected extensions include both PostgreSQL-bundled and non-bundled extensions. PostgreSQL is blocking this attack in the core server, so there's no need to modify individual extensions.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this PostgreSQL vulnerability?
The vulnerability ID for this PostgreSQL vulnerability is CVE-2022-2625.
What software versions are affected by this vulnerability?
The software versions affected by this vulnerability range from 10.0 to 14.5 of PostgreSQL.
What is the severity of CVE-2022-2625?
The severity of CVE-2022-2625 is high (8 out of 10).
How can I fix this vulnerability?
To fix this vulnerability, update your PostgreSQL software to version 14.5 or apply the appropriate patch provided by the vendor.
Where can I find more information about CVE-2022-2625?
You can find more information about CVE-2022-2625 on the official PostgreSQL website and the bugzilla pages provided in the references.