dbcve.org
PostgreSQLDatabase / datastore

CVE-2022-1552

HIGH · 8.8 CVSS v3.1 Published 2022-08-31
Fix available
A fix is available. Upgrade to 10.21 / 11.16 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in PostgreSQL. There is an issue with incomplete efforts to operate safely when a privileged user is maintaining another user's objects. The Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck commands activated relevant protections too late or not at all during the process. This flaw allows an attacker with permission to create non-temporary objects in at least one schema to execute arbitrary SQL functions under a superuser identity.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PostgreSQLDatabase / datastore
Affected:>= 10.0, < 10.21>= 11.0, < 11.16>= 12.0, < 12.11>= 13.0, < 13.7>= 14.0, < 14.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.21 / 11.16 / 12.11 or later
Fixed in 10.2111.1612.11
Vendor patch bugzilla.redhat.com →
Recommended fix High confidence

PostgreSQL 10.21, 11.16, 12.11, or 13.7 (or upgrade to latest stable 14+/15+ for longer support)

  1. 1. Back up all PostgreSQL databases using pg_dumpall or by stopping PostgreSQL and copying the data directory.
  2. 2. Verify backup integrity before proceeding with the upgrade.
  3. 3. Stop the PostgreSQL service: sudo systemctl stop postgresql (or equivalent for your system).
  4. 4. Install the fixed PostgreSQL version (10.21, 11.16, 12.11, or 13.7 depending on your current major version).
  5. 5. If upgrading to a new major version (e.g., 10 to 13), run pg_upgrade or use pg_dumpall/pg_restore to migrate data.
  6. 6. Start the PostgreSQL service: sudo systemctl start postgresql.
  7. 7. Verify the PostgreSQL version is correct: psql -c 'SELECT version();'.
  8. 8. Test application connectivity and functionality thoroughly.
Caveat Minor version upgrades within the same major version are typically safe; major version upgrades may require application compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1552 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data