|
CVE-2022-46724
|
2023-08-14 |
|
This issue was addressed by restricting... |
|
246
|
|
CVE-2022-46725
|
2023-08-14 |
|
A spoofing issue existed in the handling of...... |
|
260
|
|
CVE-2020-36615
|
2023-08-14 |
|
An out-of-bounds read was addressed with... |
|
231
|
|
CVE-2023-27939
|
2023-08-14 |
|
An out-of-bounds read was addressed with... |
|
244
|
|
CVE-2023-27947
|
2023-08-14 |
|
An out-of-bounds read was addressed with... |
|
233
|
|
CVE-2023-27948
|
2023-08-14 |
|
An out-of-bounds read was addressed with... |
|
242
|
|
CVE-2023-28179
|
2023-08-14 |
|
The issue was addressed with improved memory... |
|
201
|
|
CVE-2023-28198
|
2023-08-14 |
|
A use-after-free issue was addressed with... |
|
490
|
|
CVE-2023-28199
|
2023-08-14 |
|
An out-of-bounds read issue existed that led to...... |
|
223
|
|
CVE-2023-32358
|
2023-08-14 |
|
A type confusion issue was addressed with... |
|
293
|
