CVE-2008-2310 json
Format string vulnerability in c++filt in Apple Mac OS X 10.5 before 10.5.4 allows user-assisted attackers to execute arbitrary code or cau…
published 2008-07-01 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2306
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Format string vulnerability in c++filt in Apple Mac OS X 10.5 before 10.5.4 allows user-assisted attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted string in (1) C++ or (2) Java source code.
Patch / fix
- binutils Debian 14, Debian 13, Debian 12 2.18.1~cvs20080103-1
debian advisories DEBIAN-CVE-2008-2310
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-2310 updated
c++filt format string flaw
-
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.51% chance of exploitation in the next 30 days, higher than 84% 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
-
- CWE-134 Use of Externally-Controlled Format String
References
-
support.apple.com
/kb/HT2163
patch
-
lists.apple.com
/archives/security-announce/2008//Jun/msg00002.html
vendor-advisory
-
secunia.com
/advisories/30802
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2008/1981/references
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43494
vdb-entry
-
securitytracker.com
/id?1020392
vdb-entry
-
securityfocus.com
/bid/30018
vdb-entry
Sources
- CVE List CVE-2008-2310
- NVD CVE-2008-2310
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.