dbcve.org
PostgreSQLDatabase / datastore

CVE-2017-7486

HIGH · 7.5 CVSS v3.0 Published 2017-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 8.4 - 9.6 are vulnerable to information leak in pg_user_mappings view which discloses foreign server passwords to any user having USAGE privilege on the associated foreign server.

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's pg_user_mappings view exposes foreign server passwords to any user with USAGE privilege on the foreign server, bypassing intended access controls and allowing unauthorized disclosure of sensitive credentials that should only be visible to superusers.

MitigationRevoke USAGE privilege from non-superuser roles on affected foreign servers, or upgrade to PostgreSQL 9.6.7+, 10.2+ or later versions that contain the fix.

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:= 8.4= 8.4.1= 8.4.2= 8.4.3= 8.4.4= 8.4.5= 8.4.6= 8.4.7= 8.4.8= 8.4.9= 8.4.10= 8.4.11

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check PostgreSQL server version
    Run 'SELECT version();' or 'SHOW server_version;' to obtain the installed PostgreSQL version number
    Affected if Version is 8.4.x (any release from 8.4 through 8.4.11)
  2. Identify existing foreign servers
    Query 'SELECT srvname, srvowner FROM pg_catalog.pg_foreign_server;' to list any foreign servers configured in the database
    Affected if Any foreign servers exist in the database
  3. Check USAGE privilege on foreign servers
    Query 'SELECT * FROM information_schema.usage_privileges WHERE object_type = 'FOREIGN SERVER';' to see which roles have USAGE privilege on foreign servers
    Affected if Non-superuser roles are listed with USAGE privilege on foreign servers
  4. Verify pg_user_mappings accessibility
    As a non-superuser with USAGE on a foreign server, run 'SELECT * FROM pg_user_mappings;' to confirm the view returns data including umoptions column containing passwords
    Affected if The query returns rows and exposes sensitive credential data in umoptions to a non-superuser

A user is affected if running PostgreSQL 8.4.x AND has foreign servers with USAGE granted to non-superuser roles, allowing them to view credentials via pg_user_mappings

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Revoke USAGE privilege from non-superuser roles on affected foreign servers, or upgrade to PostgreSQL 9.6.7+, 10.2+ or later versions that contain the fix.

Fix this in PostgreSQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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