CVE-2008-2956 json
Memory leak in Pidgin 2.0.0, and possibly other versions, allows remote attackers to cause a denial of service (memory consumption) via mal…
published 2008-07-01 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2946
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Memory leak in Pidgin 2.0.0, and possibly other versions, allows remote attackers to cause a denial of service (memory consumption) via malformed XML documents. NOTE: this issue has been disputed by the upstream vendor, who states: "I was never able to identify a scenario under which a problem occurred and the original reporter wasn't able to supply any sort of reproduction details."
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-2956 updated cvss 4.3
pidgin: memory leak in XML parser
-
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
2.00% chance of exploitation in the next 30 days, higher than 80% 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-399 Resource Management Errors
References
-
securityfocus.com
/bid/29985
vdb-entry
-
openwall.com
/lists/oss-security/2008/06/27/3
mailing-list
-
secunia.com
/advisories/31387
third-party-advisory
-
securityfocus.com
/archive/1/495165/100/0/threaded
mailing-list
- crisp.cs.du.edu /?q=ca2007-1
- wiki.rpath.com /wiki/Advisories:rPSA-2008-0246
- issues.rpath.com /browse/RPL-2647
Sources
- CVE List CVE-2008-2956
- NVD CVE-2008-2956
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.