|
CVE-2023-40390
|
2024-03-28 |
|
A privacy issue was addressed by moving sensitive...... |
|
216
|
|
CVE-2023-42892
|
2024-03-28 |
|
A use-after-free issue was addressed with... |
|
210
|
|
CVE-2023-42893
|
2024-03-28 |
|
A permissions issue was addressed by removing... |
|
218
|
|
CVE-2023-42896
|
2024-03-28 |
|
An issue was addressed with improved handling of...... |
|
202
|
|
CVE-2023-42913
|
2024-03-28 |
|
This issue was addressed through improved... |
|
201
|
|
CVE-2023-42930
|
2024-03-28 |
|
This issue was addressed with improved checks.... |
|
218
|
|
CVE-2023-42931
|
2024-03-28 |
|
The issue was addressed with improved checks.... |
|
215
|
|
CVE-2023-42936
|
2024-03-28 |
|
This issue was addressed with improved... |
|
215
|
|
CVE-2023-42947
|
2024-03-28 |
|
A path handling issue was addressed with improved...... |
|
207
|
|
CVE-2023-42950
|
2024-03-28 |
|
A use after free issue was addressed with...... |
|
226
|
