CVE-2014-8835 json
The xpc_data_get_bytes function in libxpc in Apple OS X before 10.10.2 does not verify that a dictionary's Attributes key has the xpc_data…
published 2015-01-30 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-8665
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.3%
- EPSS 8.3% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
The xpc_data_get_bytes function in libxpc in Apple OS X before 10.10.2 does not verify that a dictionary's Attributes key has the xpc_data data type, which allows attackers to execute arbitrary code by providing a crafted dictionary to sysmond, related to an "XPC type confusion" issue.
Timeline
- First public exploit (EDB-35742)
- Published
Exploit prediction
8.25% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35742 Apple Mac OSX 10.9.x - sysmond XPC Privilege Escalation local, 2015-01-10
- code.google.com https://code.google.com/p/google-security-research/issues/detail?id=121 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/71992 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-19 Data Processing Errors
References
-
exploit-db.com
/exploits/35742/
exploit
-
code.google.com
/p/google-security-research/issues/detail?id=121
exploit
-
securityfocus.com
/bid/71992
vdb-entry, exploit
-
lists.apple.com
/archives/security-announce/2015/Jan/msg00003.html
vendor-advisory
-
support.apple.com
/HT204244
vendor-advisory
- packetstormsecurity.com /files/135701/OS-X-Sysmond-XPC-Type-Confusion-Privilege-Escalation.html
-
securitytracker.com
/id/1031650
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/100530
vdb-entry
Sources
- CVE List CVE-2014-8835
- NVD CVE-2014-8835
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.