CVE-2019-6214 json
A type confusion issue was addressed with improved memory handling.
published 7y ago modified 4mo ago also EUVD-2019-15781
- cvss
- 8.6
- 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
A type confusion issue was addressed with improved memory handling. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3, tvOS 12.1.2, watchOS 5.1.3. A malicious application may be able to break out of its sandbox.
Patch / fix
- Apple iOS iOS 12.1.3
- Apple macOS macOS Mojave 10.14.3
- Apple tvOS tvOS 12.1.2
- Apple watchOS watchOS 5.1.3
Is CVE-2019-6214 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-46298)
- Published
Exploit prediction
3.64% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46298 macOS < 10.14.3 / iOS < 12.1.3 - Sandbox Escapes due to Type Confusions and Memory Safety Issues in iohideventsystem dos, 2019-01-31
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.6 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/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
- Apple watchOS
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
exploit-db.com
/exploits/46298/
exploit, third-party-advisory
-
support.apple.com
/HT209446
vendor-advisory
-
support.apple.com
/HT209443
vendor-advisory
-
support.apple.com
/HT209448
vendor-advisory
-
support.apple.com
/HT209447
vendor-advisory
-
securityfocus.com
/bid/106739
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-6214
- NVD CVE-2019-6214
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.