| CVE-2019-8502 |
An API issue existed in the handling of dictation requests
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8516 |
A validation issue was addressed with improved logic
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8506 |
Exploited
Apple Multiple Products Type Confusion Vulnerability
|
8.8
High
|
Dec 18, 2019 |
| CVE-2019-8524 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8515 |
A cross-origin issue existed with the fetch API
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8523 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8514 |
A logic issue was addressed with improved state management
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8503 |
A logic issue was addressed with improved validation
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-7293 |
A memory corruption issue was addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-7292 |
A validation issue was addressed with improved logic
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-7285 |
A use after free issue was addressed with improved memory management
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-6237 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-6201 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-6207 |
An out-of-bounds read issue existed that led to the disclosure of kernel memory
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-6231 |
An out-of-bounds read was addressed with improved bounds checking
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6230 |
A memory initialization issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6229 |
A logic issue was addressed with improved validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6218 |
A memory corruption issue was addressed with improved input validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6217 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6227 |
A memory corruption issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6216 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6210 |
A memory corruption issue was addressed with improved input validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6226 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6209 |
An out-of-bounds read issue existed that led to the disclosure of kernel memory
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6215 |
A type confusion issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |