Vulnerability in PostgreSQL adminpack Extension
Summary
CVE-2018-1115: postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. Affects postgresql versions < 10.4-r0. Fixed in 10.4-r0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
PostgreSQL is an open-source relational database management system known for its robustness and scalability. The adminpack extension provides additional administrative functionality for PostgreSQL databases. However, a vulnerability has been discovered in versions before 10.4 and 9.6.9, where the pg_catalog.pg_logfile_rotate() function in the adminpack extension does not follow the same access control rules as pg_rotate_logfile. This vulnerability can be exploited by an attacker with database access to force log rotation.
Vulnerability Detail
The vulnerability (CVE-2018-1115) in the PostgreSQL adminpack extension allows an attacker with database access to manipulate log rotation. By exploiting this vulnerability, an attacker can force log rotation, potentially disrupting logging and covering their tracks. This can lead to the loss of valuable audit information and hinder forensic analysis in the event of a security incident. The vulnerability has a CVSS score of 9.1, indicating a high severity level.
How To Fix
Minimum fixed version
10.4-r0
This is the first release that contains the fix.
sudo apk add --upgrade postgresql
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update to the fixed versions as soon as possible.
Conclusion
The vulnerability in the PostgreSQL adminpack extension can be exploited by an attacker with database access to force log rotation, potentially leading to the loss of audit information. It is crucial to update to the fixed versions (10.4 or 9.6.9) to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for postgresql →
FAQ
The vulnerability allows an attacker to force log rotation, potentially leading to the loss of audit information and hindering forensic analysis.
Users of PostgreSQL versions before 10.4 and 9.6.9 with the adminpack extension enabled are affected.
No, this vulnerability requires the attacker to have database access.
There are no known instances of this vulnerability being exploited in the wild.
Yes, updating PostgreSQL to version 10.4 or 9.6.9 will fix this vulnerability.
References
Related vulnerabilities
Recent vulnerabilities recorded for postgresql.