CyberRota Analysis
AI-GeneratedPostgreSQL versions 17-18, specifically minor versions prior to 18.5 and 17.11, are vulnerable due to improper enforcement of message integrity in GSSAPI support, allowing connections to bypass pg_hba.conf rules and potentially use less secure TLS encryption. This vulnerability could lead to unauthorized data exposure if TLS settings are more permissive than GSSAPI configurations. Organizations using affected PostgreSQL versions, particularly those with sensitive data, should prioritize applying the necessary updates to mitigate this risk.
Original NVD Description
Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.