Strix
26.1K

CVE-2017-12172

UnknownEPSS 0.59%

Last modified

CVE-2017-12172 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.59% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.59%

43.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PostgresqlPostgresql9.2
PostgresqlPostgresql9.2.1
PostgresqlPostgresql9.2.2
PostgresqlPostgresql9.2.3
PostgresqlPostgresql9.2.4
PostgresqlPostgresql9.2.5
PostgresqlPostgresql9.2.6
PostgresqlPostgresql9.2.7
PostgresqlPostgresql9.2.8
PostgresqlPostgresql9.2.9
PostgresqlPostgresql9.2.10
PostgresqlPostgresql9.2.11
PostgresqlPostgresql9.2.12
PostgresqlPostgresql9.2.13
PostgresqlPostgresql9.2.14
PostgresqlPostgresql9.2.15
PostgresqlPostgresql9.2.16
PostgresqlPostgresql9.2.17
PostgresqlPostgresql9.2.18
PostgresqlPostgresql9.2.19
PostgresqlPostgresql9.2.20
PostgresqlPostgresql9.2.21
PostgresqlPostgresql9.2.22
PostgresqlPostgresql9.2.23
PostgresqlPostgresql9.3
PostgresqlPostgresql9.3.1
PostgresqlPostgresql9.3.2
PostgresqlPostgresql9.3.3
PostgresqlPostgresql9.3.4
PostgresqlPostgresql9.3.5
PostgresqlPostgresql9.3.6
PostgresqlPostgresql9.3.7
PostgresqlPostgresql9.3.8
PostgresqlPostgresql9.3.9
PostgresqlPostgresql9.3.10
PostgresqlPostgresql9.3.11
PostgresqlPostgresql9.3.12
PostgresqlPostgresql9.3.13
PostgresqlPostgresql9.3.14
PostgresqlPostgresql9.3.15
PostgresqlPostgresql9.3.16
PostgresqlPostgresql9.3.17
PostgresqlPostgresql9.3.18
PostgresqlPostgresql9.3.19
PostgresqlPostgresql9.4
PostgresqlPostgresql9.4.1
PostgresqlPostgresql9.4.2
PostgresqlPostgresql9.4.3
PostgresqlPostgresql9.4.4
PostgresqlPostgresql9.4.5

Showing 50 of 76 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

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?
Severity scoring for CVE-2017-12172 is pending analysis. The EPSS model estimates a 0.59% probability of exploitation in the next 30 days.
How do I fix CVE-2017-12172?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-12172?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST