| CVE-2019-6222 |
A consistency issue was addressed with improved state handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-6204 |
A logic issue was addressed with improved validation
|
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-6221 |
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-6219 |
A denial of service issue was addressed with improved validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6228 |
A cross-site scripting issue existed in Safari
|
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-6211 |
A memory corruption issue was addressed with improved state management
|
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 |
| CVE-2019-6208 |
A memory initialization issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6200 |
An out-of-bounds read was addressed with improved input validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6225 |
A memory corruption issue was addressed with improved validation
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6234 |
A memory corruption issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6214 |
A type confusion issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6224 |
A buffer overflow issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6213 |
A buffer overflow was addressed with improved bounds checking
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6233 |
A memory corruption issue was addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |