CVE-2019-6205: High severity tvos vulnerability
Kernel. A memory corruption issue was addressed with improved lock state checking.
Other sources
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.
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2019-6235
- CVE-2019-6231
- CVE-2019-6230
- CVE-2019-6224
- CVE-2019-6214
- CVE-2019-6225
- CVE-2019-6210
- CVE-2019-6205
- CVE-2019-6213
- CVE-2019-6209
- CVE-2019-6208
- CVE-2019-6218
- CVE-2018-20346
- CVE-2018-20505
- CVE-2018-20506
- CVE-2019-6227
- CVE-2019-6233
- CVE-2019-6234
- CVE-2019-6229
- CVE-2019-6215
- CVE-2019-6212
- CVE-2019-6216
- CVE-2019-6217
- CVE-2019-6226
- CVE-2019-8570
- CVE-2019-6200
- CVE-2019-6202
- CVE-2019-6221
- CVE-2018-4467
- CVE-2018-4452
- CVE-2019-6219
- CVE-2019-6220
- CVE-2019-6211
- CVE-2019-6206
- CVE-2019-6228
Frequently Asked Questions
What is CVE-2019-6205?
CVE-2019-6205 refers to a memory corruption issue that was addressed with improved lock state checking in Apple iOS 12.1.3, macOS Mojave 10.14.3, and tvOS 12.1.2.
How severe is CVE-2019-6205?
CVE-2019-6205 has a severity level of 7.8 (high).
What systems are affected by CVE-2019-6205?
CVE-2019-6205 affects Apple iOS up to version 12.1.3, macOS Mojave up to version 10.14.3, and tvOS up to version 12.1.2.
How can a malicious application exploit CVE-2019-6205?
A malicious application can exploit CVE-2019-6205 to cause unexpected changes in memory shared between processes.
Where can I find more information about CVE-2019-6205?
You can find more information about CVE-2019-6205 on the following sources: [Packet Storm Security](http://packetstormsecurity.com/files/156051/XNU-vm_map_copy-Insufficient-Fix.html), [SecurityFocus](http://www.securityfocus.com/bid/106695), and [Apple Support](https://support.apple.com/HT209443).