CVE-2017-12172
CVE-2017-12172 is a medium-severity vulnerability in Postgresql with a CVSS 3.x base score of 6.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-59.
Key facts
- Severity: Medium (CVSS 3.x base score 6.7)
- CVSS v2: 7.2
- EPSS exploit prediction: 1% (44th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-59
- Affected product: Postgresql
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is 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.
- How severe is CVE-2017-12172?
- CVE-2017-12172 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2017-12172 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-12172?
- CVE-2017-12172 primarily affects Postgresql. In total, 76 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2017-12172?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2017-12172 published?
- CVE-2017-12172 was published on 2017-11-22 and last updated on 2026-06-17.
References
- http://www.securityfocus.com/bid/101949
- http://www.securitytracker.com/id/1039752
- https://access.redhat.com/errata/RHSA-2017:3402
- https://access.redhat.com/errata/RHSA-2017:3403
- https://access.redhat.com/errata/RHSA-2017:3404
- https://access.redhat.com/errata/RHSA-2017:3405
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
Affected products (76)
- cpe:2.3:a:postgresql:postgresql:9.2:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.1:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.2:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.3:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.4:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.5:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.6:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.7:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.8:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.9:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.10:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.11:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.12:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.13:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.14:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.15:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.16:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.17:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.18:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.19:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.20:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.21:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.22:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.2.23:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.1:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.2:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.3:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.4:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.5:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.6:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.7:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.8:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.9:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.10:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.11:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.12:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.13:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.14:*:*:*:*:*:*:*
- cpe:2.3:a:postgresql:postgresql:9.3.15:*:*:*:*:*:*:*
More vulnerabilities in Postgresql
- CVE-2013-1903 — Critical (CVSS 10.0): PostgreSQL, possibly 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before…
- CVE-2013-1902 — Critical (CVSS 10.0): PostgreSQL, 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before 8.3.23…
- CVE-2007-3279 — Critical (CVSS 10.0): PostgreSQL 8.1 and probably later versions, when the PL/pgSQL (plpgsql) language has been created, grants certain…
- CVE-2002-1399 — Critical (CVSS 10.0): Unknown vulnerability in cash_out and possibly other functions in PostgreSQL 7.2.1 and earlier, and possibly later…
- CVE-2015-0244 — Critical (CVSS 9.8): PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not…
- CVE-2015-3166 — Critical (CVSS 9.8): The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7,…
All CVEs affecting Postgresql →
Other CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities
- CVE-2024-37143 — Critical (CVSS 10.0): Dell PowerFlex appliance versions prior to IC 46.381.00 and IC 46.376.00, Dell PowerFlex rack versions prior to RCM…
- CVE-2024-28189 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file…
- CVE-2024-28185 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application does not account for symlinks placed inside the…
- CVE-2022-22995 — Critical (CVSS 10.0): The combination of primitives offered by SMB and AFP in their default configuration allows the arbitrary writing of…
- CVE-2014-4480 — Critical (CVSS 10.0): Directory traversal vulnerability in afc in AppleFileConduit in Apple iOS before 8.1.3 and Apple TV before 7.0.3 allows…
- CVE-2002-2374 — Critical (CVSS 10.0): Unspecified vulnerability in pprosetup in Sun PatchPro 2.0 has unknown impact and attack vectors related to "unsafe use…
Browse all CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities →