|
CVE-2023-27930
|
2023-06-23 |
|
A type confusion issue was addressed with... |
|
389
|
|
CVE-2023-28191
|
2023-06-23 |
|
This issue was addressed with improved... |
|
375
|
|
CVE-2023-28202
|
2023-06-23 |
|
This issue was addressed with improved state... |
|
353
|
|
CVE-2023-28204
|
2023-06-23 |
|
An out-of-bounds read was addressed with... |
|
417
|
|
CVE-2023-32354
|
2023-06-23 |
|
An out-of-bounds read was addressed with... |
|
351
|
|
CVE-2023-32357
|
2023-06-23 |
|
An authorization issue was addressed with... |
|
392
|
|
CVE-2023-32368
|
2023-06-23 |
|
An out-of-bounds read was addressed with... |
|
400
|
|
CVE-2023-32372
|
2023-06-23 |
|
An out-of-bounds read was addressed with... |
|
391
|
|
CVE-2023-32373
|
2023-06-23 |
|
A use-after-free issue was addressed with... |
|
358
|
|
CVE-2023-32376
|
2023-06-23 |
|
This issue was addressed with improved... |
|
358
|
