dbcve.org
PostgreSQLDatabase / datastore

CVE-2017-7548

HIGH · 7.5 CVSS v3.1 Published 2017-08-16
Fix available
A fix is available. Upgrade to 9.4.13 / 9.5.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
PostgreSQL versions before 9.4.13, 9.5.8 and 9.6.4 are vulnerable to authorization flaw allowing remote authenticated attackers with no privileges on a large object to overwrite the entire contents of the object, resulting in a denial of service.

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 · high confidence

PostgreSQL versions before 9.4.13, 9.5.8, and 9.6.4 contain an authorization flaw in the large object subsystem. Authenticated remote attackers with no privileges on a specific large object can overwrite its entire contents, causing denial of service.

MitigationUpgrade PostgreSQL to version 9.4.13, 9.5.8, 9.6.4 or later. Alternatively, revoke CREATE privilege for large objects from untrusted users until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 9.4, < 9.4.13>= 9.5, < 9.5.8>= 9.6, < 9.6.4
Debian LinuxOperating system
Affected:= 8.0= 9.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed PostgreSQL version
    Run 'psql --version' from command line, or connect to the database and run 'SELECT version();' to see the full version string
    Affected if The version is 9.4.x before 9.4.13, 9.5.x before 9.5.8, or 9.6.x before 9.6.4
  2. Check if large objects exist in the database
    Connect to the database as a superuser and run: SELECT COUNT(*) FROM pg_largeobject;
    Affected if Large objects exist in the database (count > 0)
  3. Verify large object privilege model
    Run: SELECT lo_name, lo_oid, lom_owner::regrole FROM pg_largeobject_metadata; to see large object owners
    Affected if Multiple database users have access to the database and large objects exist, as the flaw allows any authenticated user to overwrite LOs they do not own

You are affected if your PostgreSQL version is before 9.4.13, 9.5.8, or 9.6.4 AND your database contains large objects that could be accessed by untrusted authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 9.4.13 / 9.5.8 / 9.6.4 or later
Fixed in 9.4.139.5.89.6.4
Interim mitigation

Upgrade PostgreSQL to version 9.4.13, 9.5.8, 9.6.4 or later. Alternatively, revoke CREATE privilege for large objects from untrusted users until patching can be completed.

Fix this in PostgreSQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,704.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7548 — 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-2017-7548 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