CVE-2018-4090 json
An issue was discovered in certain Apple products.
published 8y ago modified 4mo ago also EUVD-2018-15876
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in certain Apple products. iOS before 11.2.5 is affected. macOS before 10.13.3 is affected. tvOS before 11.2.5 is affected. watchOS before 4.2.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 apple_tv 11.2.5
- apple iphone_os 11.2.5
- apple mac_os_x 10.13.3
- apple watchos 4.2.2
Is CVE-2018-4090 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-43923)
- Published
Exploit prediction
3.62% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43923 macOS - 'sysctl_vfs_generic_conf' Stack Leak Through Struct Padding dos, 2018-01-29
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/43923/
exploit, third-party-advisory, vdb-entry
-
support.apple.com
/HT208462
vendor-advisory
-
support.apple.com
/HT208465
vendor-advisory
-
support.apple.com
/HT208464
vendor-advisory
-
support.apple.com
/HT208463
vendor-advisory
-
securitytracker.com
/id/1040265
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102782
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1040267
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-4090
- NVD CVE-2018-4090
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.