CVE-2017-7485
CVE-2017-7485 Vulnerability Analysis & Exploit Intelligence
In PostgreSQL 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, it was found that the PGREQUIRESSL environment variable was no longer enforcing a SSL/TLS connection to a PostgreSQL server. An active Man-in-the-Middle attacker could use this flaw to strip the SSL/TLS protection from a connection between a client and a server.
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
2%
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-390
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /TLS.
References
9 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
- www.postgresql.org/about/news/1746/
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2017:1838
vendor-advisory, x_refsource_REDHAT
- www.securityfocus.com/bid/98461
vdb-entry, x_refsource_BID
Elsewhere on this site
- the postgresql global development groupevery CVE for this vendor
- CWE-390other 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.