Skip to content
Fencer Intel
medium 4.0

CVE-2009-3229 json

The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, and 8.2 before 8.2.14 allows remote authenticated users to caus…

published 17y ago modified 4mo ago also EUVD-2009-3212

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

Summary

The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, and 8.2 before 8.2.14 allows remote authenticated users to cause a denial of service (backend shutdown) by "re-LOAD-ing" libraries from a certain plugins directory.

Patch / fix

  • 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

Is CVE-2009-3229 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-3229 updated cvss 4.0

postgresql: authenticated user server DoS via plugin re-LOAD-ing

  • 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

2.61% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

Classification

Technology feeds

References

Sources

Fencer Intel 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.