CVE-2017-7484
CVE-2017-7484 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Weakness & attack patterns
- CWE-285
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
- T1083File and Directory Discovery
- T1562.003Impair Defenses: Impair Command History Logging
References
10 on the record
- www.securitytracker.com/id/1038476
vdb-entry, x_refsource_SECTRACK
- www.debian.org/security/2017/dsa-3851
vendor-advisory, x_refsource_DEBIAN
- access.redhat.com/errata/RHSA-2017:2425
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2017:1678
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2017:1677
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2017:1983
vendor-advisory, x_refsource_REDHAT
- www.postgresql.org/about/news/1746/
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2017:1838
vendor-advisory, x_refsource_REDHAT
Elsewhere on this site
- the postgresql global development groupevery CVE for this vendor
- CWE-285other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.