| CVE-2019-6208 |
A memory initialization issue was addressed with improved memory handling
|
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 |
| CVE-2019-6205 |
A memory corruption issue was addressed with improved lock state checking
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6212 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6235 |
A memory corruption issue was addressed with improved validation
|
Not rated
|
Mar 4, 2019 |
| CVE-2018-4233 |
An issue was discovered in certain Apple products
|
8.8
High
|
Jun 8, 2018 |