CVE-2017-12172
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with an admin-level account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 6.7 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-59
- Record status
- Modified
Affected
- PostgreSQL 9.2
- PostgreSQL 9.2.1
- PostgreSQL 9.2.2
- PostgreSQL 9.2.3
- PostgreSQL 9.2.4
- PostgreSQL 9.2.5
- PostgreSQL 9.2.6
- PostgreSQL 9.2.7
Attack profile CVSS 3.0 · 6.7
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-12172.md and follow it. Check whether this project is affected by CVE-2017-12172. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
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/
- 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/