| CVE-2023-40393 |
An authentication issue was addressed with improved state management
|
7.5
Élevée
|
10 janv. 2024 |
| CVE-2023-40433 |
A logic issue was addressed with improved checks
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-32366 |
An out-of-bounds write issue was addressed with improved input validation
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-28197 |
An access issue was addressed with additional sandbox restrictions
|
3.3
Faible
|
10 janv. 2024 |
| CVE-2022-32931 |
This issue was addressed with improved data protection
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-42933 |
This issue was addressed with improved checks
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-40430 |
A logic issue was addressed with improved checks
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-42876 |
The issue was addressed with improved bounds checks
|
7.1
Élevée
|
10 janv. 2024 |
| CVE-2023-42929 |
The issue was addressed with improved checks
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-40411 |
This issue was addressed with improved data protection
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2022-47915 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-41060 |
A type confusion issue was addressed with improved checks
|
8.8
Élevée
|
10 janv. 2024 |
| CVE-2023-41987 |
This issue was addressed with improved checks
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2022-48577 |
An access issue was addressed with improved access restrictions
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-38607 |
The issue was addressed with improved handling of caches
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-32436 |
The issue was addressed with improved bounds checks
|
7.1
Élevée
|
10 janv. 2024 |
| CVE-2023-42831 |
This issue was addressed by removing the vulnerable code
|
5.5
Moyenne
|
10 janv. 2024 |
| CVE-2023-42866 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
10 janv. 2024 |
| CVE-2023-42870 |
A use-after-free issue was addressed with improved memory management
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-42826 |
The issue was addressed with improved checks
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-42934 |
An information disclosure issue was addressed by removing the vulnerable code
|
4.2
Moyenne
|
10 janv. 2024 |
| CVE-2023-42830 |
A privacy issue was addressed with improved private data redaction for log entries
|
3.3
Faible
|
10 janv. 2024 |
| CVE-2023-42871 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
10 janv. 2024 |
| CVE-2023-38610 |
A memory corruption issue was addressed by removing the vulnerable code
|
7.1
Élevée
|
10 janv. 2024 |
| CVE-2023-40437 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.5
Moyenne
|
10 janv. 2024 |