Skip to content
Fencer Vulns
medium 6.8

CVE-2009-3231 json

The core server component in PostgreSQL 8.3 before 8.3.8 and 8.2 before 8.2.14, when using LDAP authentication with anonymous binds, allows…

published 2009-09-17 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3214

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.6%
EPSS 7.6% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

The core server component in PostgreSQL 8.3 before 8.3.8 and 8.2 before 8.2.14, when using LDAP authentication with anonymous binds, allows remote attackers to bypass authentication via an empty password.

Patch / fix

  • postgresql postgresql 8.2.14, 8.3.8
  • php RHEL 2 APPLICATION_STACK 5.2.10-1.el5s2
  • httpd RHEL 2 APPLICATION_STACK 2.2.13-2.el5s2
  • mysql RHEL 2 APPLICATION_STACK 5.0.84-2.el5s2
  • php-gd RHEL 2 APPLICATION_STACK 5.2.10-1.el5s2
  • mod_ssl RHEL 2 APPLICATION_STACK 1:2.2.13-2.el5s2
  • php-cli RHEL 2 APPLICATION_STACK 5.2.10-1.el5s2
  • php-dba RHEL 2 APPLICATION_STACK 5.2.10-1.el5s2
  • php-pdo RHEL 2 APPLICATION_STACK 5.2.10-1.el5s2

red hat advisories RHSA-2009:1461

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-3231 updated cvss 6.8

postgresql: LDAP authentication bypass when anonymous LDAP bind are allowed

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.57% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.