PostgreSQLDatabase / datastore
CVE-2017-7484
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 · uneditedIt was found that some selectivity estimation functions in PostgreSQL before 9.2.21, 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3 did not check user privileges before providing information from pg_statistic, possibly leaking information. An unprivileged attacker could use this flaw to steal some information from tables they are otherwise not allowed to access.
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 confidencePostgreSQL selectivity estimation functions failed to check user privileges before querying pg_statistic, allowing unprivileged attackers to extract statistical information about tables they should not have access to, potentially revealing sensitive data through the query planner.
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
<= 9.2.20= 9.3= 9.3.1= 9.3.2= 9.3.3= 9.3.4= 9.3.5= 9.3.6= 9.3.7= 9.3.8= 9.3.9= 9.3.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PostgreSQL versionRun 'psql -c "SELECT version();"' or check the postgresql-server package version with 'rpm -q postgresql-server' (RHEL) or 'dpkg -l postgresql' (Debian)Affected if The version is 9.2.20 or earlier, or any 9.3.x version through 9.3.10
-
Identify users with database connect permissionRun 'psql -c "SELECT datname, rolname FROM pg_database d JOIN pg_roles r ON d.datacl IS NOT NULL WHERE NOT (d.datacl & '=r"' || rolname) = 0;' or check pg_database catalog for non-owner accessAffected if Untrusted or unprivileged users have CONNECT privilege on any database
-
Verify pg_statistic ACL permissionsRun 'psql -c "SELECT relname, relacl FROM pg_class WHERE relname = 'pg_statistic';"'Affected if Unprivileged users have SELECT permission on pg_statistic (relacl shows any role other than postgres or owner with access)
-
Check for untrusted roles with broad permissionsRun 'psql -c "SELECT rolname, rolconnlimit, rolcanlogin FROM pg_roles WHERE rolcanlogin = true AND rolname NOT LIKE 'pg_%';"' to list login-capable rolesAffected if There are non-system roles with login capability that should not have access to sensitive table statistics
You are affected if running PostgreSQL 9.2.20 or earlier or any 9.3.x through 9.3.10 AND unprivileged users have database CONNECT permissions and SELECT access to pg_statistic.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade PostgreSQL to version 9.2.21, 9.3.17, 9.4.12, 9.5.7, 9.6.3 or later. Alternatively, restrict access to pg_statistic and ensure untrusted users have no database access.
Fix this in PostgreSQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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