First published: Wed Sep 09 2009(Updated: )
Quoting upstream PostgreSQL security page: <a href="http://www.postgresql.org/support/security.html">http://www.postgresql.org/support/security.html</a> If PostgreSQL is configured with LDAP authentication, and your LDAP configuration allows anonymous binds, it is possible for a user to authenticate themselves with an empty password. Affected versions: 8.3, 8.2 Fixed in versions: 8.3.8, 8.2.14 Severity: A - A vulnerability that is exploitable for privilege escalation without requiring a prior login.
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL Common | >=8.2<8.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-522084 is medium as it involves potential unauthorized access through LDAP authentication.
To fix REDHAT-BUG-522084, configure your LDAP to disallow anonymous binds when using PostgreSQL.
PostgreSQL versions 8.2 to 8.3 are affected by REDHAT-BUG-522084.
REDHAT-BUG-522084 describes a vulnerability related to LDAP authentication allowing for anonymous binds.
No, REDHAT-BUG-522084 specifically pertains to PostgreSQL configured with LDAP authentication.