| CVE-2019-8523 |
Multiple memory corruption issues were addressed with improved memory handling
|
Not rated
|
Dec 18, 2019 |
| CVE-2019-8503 |
A logic issue was addressed with improved validation
|
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-6221 |
An out-of-bounds read was addressed with improved bounds checking
|
Not rated
|
Mar 5, 2019 |
| CVE-2019-6229 |
A logic issue was addressed with improved 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-6226 |
Multiple memory corruption issues were addressed with improved memory handling
|
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-6234 |
A memory corruption issue was addressed with improved memory handling
|
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-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 |