Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-7484

postgresql: Selectivity estimators bypass SELECT privilege checks

Overview

Published
12 May 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
35 OS packages
2 Linux distributions
Yes Fix available

Description

It 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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
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

Weakness: CWE-285, CWE-200

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 5 fixes

Oracle Linux 1 release · 1 package

fixed 1
postgresql
Oracle Linux fixes for CVE-2017-7484
ReleasePackageFixed in
7 postgresql +11 9.2.21-1.el7

Red Hat 2 releases · 3 packages

fixed 4
rh-postgresql95-postgresql postgresql rh-postgresql94-postgresql
Red Hat fixes for CVE-2017-7484
ReleasePackageFixed inAdvisory
rh-postgresql95-postgresql +4 0:9.5.7-2.el6 RHSA-2017:1838
7 postgresql +11 0:9.2.21-1.el7 RHSA-2017:1983
7 rh-postgresql94-postgresql +11 0:9.4.12-1.el7 RHSA-2017:1678
7 rh-postgresql95-postgresql +10 0:9.5.7-2.el7 RHSA-2017:1677

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.