PostgreSQL Fix Requires Server Updates and Rebuilding C Extensions
Updating PostgreSQL alone is insufficient to fully address a type confusion vulnerability that allows database users with object creation privileges to execute code on the server. According to The Hacker News, administra
Updating PostgreSQL alone is insufficient to fully address a type confusion vulnerability that allows database users with object creation privileges to execute code on the server. According to The Hacker News, administrators must also rebuild every installed extension written in C to obtain full protection.
Scope and exploitation status
The executed code runs with the privileges of the operating system account running PostgreSQL. This establishes the impact described in the article; it does not establish execution with the operating systemβs highest administrative privileges.
Researcher Mehmet Ince described a working exploit and demonstrated it on PostgreSQL 18.6. However, the PostgreSQL Global Development Group has not reported any attacks using the vulnerability. The demonstration supports prioritizing remediation, but does not establish that a particular organization has been compromised.
Affected releases are versions before 18.7, 17.12, 16.16, 15.20 and 14.25 in their respective branches. The corresponding update targets are 18.7, 17.12, 16.16, 15.20 or 14.25, depending on the major version in use.
TMGS recommendations
TMGS recommends including both the server update and C extension rebuilds in the maintenance plan:
- Inventory PostgreSQL servers, their release branches and all installed C extensions.
- Verify backup recovery capability, then test the update and extension rebuilds in a test environment before deployment.
- Retain evidence of the resulting server version, each C extension rebuild and application checks after maintenance.
- Review which database accounts need object creation privileges, and limit the PostgreSQL operating system accountβs permissions to operational needs.
For organizations using an external database administrator, TMGS recommends explicitly assigning responsibility for rebuilding extensions, testing and delivering results. A statement that PostgreSQL has been updated does not establish that the extension work required for full protection is complete.
Read the full analysis on TMGS: https://tmgs.vn/tin-tuc/va-postgresql-phai-tinh-ca-phan-mo-rong-viet-bang-c-i.41e26a31-7b24-4fb5-9eec-90f0655235e1
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.