CVE-2019-6213 json
A buffer overflow was addressed with improved bounds checking.
published 7y ago modified 4mo ago also EUVD-2019-15780
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.4%
- EPSS 5.4% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
A buffer overflow was addressed with improved bounds checking. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3, tvOS 12.1.2, watchOS 5.1.3. An application may be able to execute arbitrary code with kernel privileges.
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-6213 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-46300)
- Published
Exploit prediction
5.42% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46300 macOS < 10.14.3 / iOS < 12.1.3 - Kernel Heap Overflow in PF_KEY due to Lack of Bounds Checking when Retrieving Statistics 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 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Apple iOS
- Apple macOS
- Apple tvOS
- Apple watchOS
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/46300/
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-6213
- NVD CVE-2019-6213
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.