Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2017-12172


PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, 9.5.x before 9.5.10, 9.4.x before 9.4.15, 9.3.x before 9.3.20, and 9.2.x before 9.2.24 runs under a non-root operating system account, and database superusers have effective ability to run arbitrary code under that system account. PostgreSQL provides a script for starting the database server during system boot. Packages of PostgreSQL for many operating systems provide their own, packager-authored startup implementations. Several implementations use a log file name that the database superuser can replace with a symbolic link. As root, they open(), chmod() and/or chown() this log file name. This often suffices for the database superuser to escalate to root privileges when root starts the server.


Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.7, requiring local system access to exploit with relatively low complexity without requiring user interaction . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from postgresql organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.


Published

2017-11-22T19:29:00.223

Last Modified

2026-06-17T01:02:50.150

Status

Modified

Source

[email protected]

Severity

CVSSv3.0: 6.7 (MEDIUM)

CVSSv2 Vector

AV:L/AC:L/Au:N/C:C/I:C/A:C

  • Access Vector: LOCAL
  • Access Complexity: LOW
  • Authentication: NONE
  • Confidentiality Impact: COMPLETE
  • Integrity Impact: COMPLETE
  • Availability Impact: COMPLETE
Exploitability Score

3.9

Impact Score

10.0

Weaknesses
  • Type: Secondary
    CWE-59
  • Type: Primary
    CWE-59

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application postgresql postgresql 9.2 Yes
Application postgresql postgresql 9.2.1 Yes
Application postgresql postgresql 9.2.2 Yes
Application postgresql postgresql 9.2.3 Yes
Application postgresql postgresql 9.2.4 Yes
Application postgresql postgresql 9.2.5 Yes
Application postgresql postgresql 9.2.6 Yes
Application postgresql postgresql 9.2.7 Yes
Application postgresql postgresql 9.2.8 Yes
Application postgresql postgresql 9.2.9 Yes
Application postgresql postgresql 9.2.10 Yes
Application postgresql postgresql 9.2.11 Yes
Application postgresql postgresql 9.2.12 Yes
Application postgresql postgresql 9.2.13 Yes
Application postgresql postgresql 9.2.14 Yes
Application postgresql postgresql 9.2.15 Yes
Application postgresql postgresql 9.2.16 Yes
Application postgresql postgresql 9.2.17 Yes
Application postgresql postgresql 9.2.18 Yes
Application postgresql postgresql 9.2.19 Yes
Application postgresql postgresql 9.2.20 Yes
Application postgresql postgresql 9.2.21 Yes
Application postgresql postgresql 9.2.22 Yes
Application postgresql postgresql 9.2.23 Yes
Application postgresql postgresql 9.3 Yes
Application postgresql postgresql 9.3.1 Yes
Application postgresql postgresql 9.3.2 Yes
Application postgresql postgresql 9.3.3 Yes
Application postgresql postgresql 9.3.4 Yes
Application postgresql postgresql 9.3.5 Yes
Application postgresql postgresql 9.3.6 Yes
Application postgresql postgresql 9.3.7 Yes
Application postgresql postgresql 9.3.8 Yes
Application postgresql postgresql 9.3.9 Yes
Application postgresql postgresql 9.3.10 Yes
Application postgresql postgresql 9.3.11 Yes
Application postgresql postgresql 9.3.12 Yes
Application postgresql postgresql 9.3.13 Yes
Application postgresql postgresql 9.3.14 Yes
Application postgresql postgresql 9.3.15 Yes
Application postgresql postgresql 9.3.16 Yes
Application postgresql postgresql 9.3.17 Yes
Application postgresql postgresql 9.3.18 Yes
Application postgresql postgresql 9.3.19 Yes
Application postgresql postgresql 9.4 Yes
Application postgresql postgresql 9.4.1 Yes
Application postgresql postgresql 9.4.2 Yes
Application postgresql postgresql 9.4.3 Yes
Application postgresql postgresql 9.4.4 Yes
Application postgresql postgresql 9.4.5 Yes
Application postgresql postgresql 9.4.6 Yes
Application postgresql postgresql 9.4.7 Yes
Application postgresql postgresql 9.4.8 Yes
Application postgresql postgresql 9.4.9 Yes
Application postgresql postgresql 9.4.10 Yes
Application postgresql postgresql 9.4.11 Yes
Application postgresql postgresql 9.4.12 Yes
Application postgresql postgresql 9.4.13 Yes
Application postgresql postgresql 9.4.14 Yes
Application postgresql postgresql 9.5 Yes
Application postgresql postgresql 9.5.1 Yes
Application postgresql postgresql 9.5.2 Yes
Application postgresql postgresql 9.5.3 Yes
Application postgresql postgresql 9.5.4 Yes
Application postgresql postgresql 9.5.5 Yes
Application postgresql postgresql 9.5.6 Yes
Application postgresql postgresql 9.5.7 Yes
Application postgresql postgresql 9.5.8 Yes
Application postgresql postgresql 9.5.9 Yes
Application postgresql postgresql 9.6 Yes
Application postgresql postgresql 9.6.1 Yes
Application postgresql postgresql 9.6.2 Yes
Application postgresql postgresql 9.6.3 Yes
Application postgresql postgresql 9.6.4 Yes
Application postgresql postgresql 9.6.5 Yes
Application postgresql postgresql 10 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For postgresql's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.