CVE-2017-13869 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-5384
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- 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 bypass intended memory-read restrictions 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-43319)
- Published
Exploit prediction
4.74% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43319 Apple macOS - 'getrusage' Stack Leak Through struct Padding dos, 2017-12-11
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
exploit-db.com
/exploits/43319/
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-13869
- NVD CVE-2017-13869
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.