CVE-2008-2829 json
php_imap.c in PHP 5.2.5, 5.2.6, 4.x, and other versions, uses obsolete API calls that allow context-dependent attackers to cause a denial o…
published 2008-06-23 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2822
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.3%
- EPSS 5.3% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
php_imap.c in PHP 5.2.5, 5.2.6, 4.x, and other versions, uses obsolete API calls that allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long IMAP request, which triggers an "rfc822.c legacy routine buffer overflow" error message, related to the rfc822_write_address function.
Patch / fix
- securityfocus.com/bid/29829 advisory
- vupen.com/english/advisories/2009/1297 advisory
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-2008-2829 updated
php: ext/imap legacy routine buffer overflow
-
Red Hat All currently supported Red Hat productsnot 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
5.27% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
securityfocus.com
/bid/29829
vdb-entry, patch, third-party-advisory
-
vupen.com
/english/advisories/2009/1297
vdb-entry, patch, third-party-advisory
-
marc.info
/?l=bugtraq&m=125631037611762&w=2
vendor-advisory, mailing-list, third-party-advisory
-
security.gentoo.org
/glsa/glsa-200811-05.xml
vendor-advisory, third-party-advisory
-
marc.info
/?l=bugtraq&m=124654546101607&w=2
vendor-advisory, mailing-list, third-party-advisory
-
redhat.com
/archives/fedora-package-announce/2009-May/msg01451.html
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:128
vendor-advisory, third-party-advisory
-
ubuntu.com
/usn/usn-628-1
vendor-advisory, third-party-advisory
-
lists.apple.com
/archives/security-announce/2009/May/msg00002.html
vendor-advisory, mailing-list, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2008-12/msg00002.html
vendor-advisory, third-party-advisory
-
redhat.com
/archives/fedora-package-announce/2009-May/msg01465.html
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:126
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:127
vendor-advisory, third-party-advisory
-
bugs.php.net
/bug.php?id=42862
vendor-advisory
-
openwall.com
/lists/oss-security/2008/06/24/2
mailing-list, third-party-advisory
-
secunia.com
/advisories/32746
third-party-advisory
-
support.apple.com
/kb/HT3549
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43357
vdb-entry, third-party-advisory
-
securityfocus.com
/archive/1/501376/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
wiki.rpath.com
/Advisories:rPSA-2009-0035
broken-link
-
secunia.com
/advisories/35074
third-party-advisory
-
openwall.com
/lists/oss-security/2008/06/19/6
mailing-list, third-party-advisory
-
secunia.com
/advisories/31200
third-party-advisory
-
osvdb.org
/46641
vdb-entry, broken-link
-
us-cert.gov
/cas/techalerts/TA09-133A.html
third-party-advisory, us-government-resource
-
secunia.com
/advisories/35306
third-party-advisory
-
bugs.gentoo.org
/show_bug.cgi?id=221969
third-party-advisory
-
secunia.com
/advisories/35650
third-party-advisory
Sources
- CVE List CVE-2008-2829
- NVD CVE-2008-2829
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.