First published: Tue Aug 02 2022(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/postgresql | <14.5 | 14.5 |
redhat/postgresql | <13.8 | 13.8 |
redhat/postgresql | <12.12 | 12.12 |
redhat/postgresql | <11.17 | 11.17 |
redhat/postgresql | <10.22 | 10.22 |
PostgreSQL PostgreSQL | >=10.0<10.22 | |
PostgreSQL PostgreSQL | >=11.0<11.17 | |
PostgreSQL PostgreSQL | >=12.0<12.12 | |
PostgreSQL PostgreSQL | >=13.0<13.8 | |
PostgreSQL PostgreSQL | >=14.0<14.5 | |
PostgreSQL PostgreSQL | =15-beta1 | |
PostgreSQL PostgreSQL | =15-beta2 | |
Fedoraproject Fedora | =36 | |
Redhat Enterprise Linux | =6.0 | |
Redhat Enterprise Linux | =7.0 | |
Redhat Enterprise Linux | =8.0 | |
Redhat Enterprise Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this PostgreSQL vulnerability is CVE-2022-2625.
The software versions affected by this vulnerability range from 10.0 to 14.5 of PostgreSQL.
The severity of CVE-2022-2625 is high (8 out of 10).
To fix this vulnerability, update your PostgreSQL software to version 14.5 or apply the appropriate patch provided by the vendor.
You can find more information about CVE-2022-2625 on the official PostgreSQL website and the bugzilla pages provided in the references.