CVE-2019-6205 json
A memory corruption issue was addressed with improved lock state checking.
published 7y ago modified 4mo ago also EUVD-2019-15772
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
A memory corruption issue was addressed with improved lock state checking. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3, tvOS 12.1.2. A malicious application may cause unexpected changes in memory shared between processes.
Patch / fix
- Apple iOS iOS 12.1.3
- Apple macOS macOS Mojave 10.14.3
- Apple tvOS tvOS 12.1.2
Is CVE-2019-6205 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-46299)
- Published
Exploit prediction
4.07% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46299 macOS < 10.14.3 / iOS < 12.1.3 XNU - 'vm_map_copy' Optimization which Requires Atomicity isn't Atomic dos, 2019-01-31
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 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Apple iOS
- Apple macOS
- Apple tvOS
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
exploit-db.com
/exploits/46299/
exploit, third-party-advisory, vdb-entry
-
support.apple.com
/HT209446
vendor-advisory
-
support.apple.com
/HT209443
vendor-advisory
-
support.apple.com
/HT209447
vendor-advisory
-
securityfocus.com
/bid/106695
vdb-entry, third-party-advisory
- packetstormsecurity.com /files/156051/XNU-vm_map_copy-Insufficient-Fix.html
Sources
- CVE List CVE-2019-6205
- NVD CVE-2019-6205
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.