CVE-2017-13876 json
An issue was discovered in certain Apple products.
published 2017-12-25 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5391
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.1%
- EPSS 5.1% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in certain Apple products. iOS before 11.2 is affected. macOS before 10.13.2 is affected. tvOS before 11.2 is affected. watchOS before 4.2 is affected. The issue involves the "Kernel" component. It allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app.
Patch / fix
- apple iphone_os 11.2
- apple mac_os_x 10.13.2
- apple tvos 11.2
- apple watchos 4.2
Timeline
- First public exploit (EDB-43325)
- Published
Exploit prediction
5.11% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-43325 Apple XNU Kernel - Memory Corruption due to Integer Overflow in __offsetof Usage in posix_spawn on 32-bit Platforms dos, 2017-12-12
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/43325/
exploit, third-party-advisory, vdb-entry
-
support.apple.com
/HT208331
vendor-advisory
-
support.apple.com
/HT208327
vendor-advisory
-
support.apple.com
/HT208325
vendor-advisory
-
support.apple.com
/HT208334
vendor-advisory
-
securitytracker.com
/id/1039966
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1039953
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1039952
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102100
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-13876
- NVD CVE-2017-13876
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.