| CVE-2024-40796 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.3
Medium
|
Jul 29, 2024 |
| CVE-2024-40779 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Jul 29, 2024 |
| CVE-2024-40778 |
An authentication issue was addressed with improved state management
|
3.3
Low
|
Jul 29, 2024 |
| CVE-2024-40806 |
An out-of-bounds read issue was addressed with improved input validation
|
5.5
Medium
|
Jul 29, 2024 |
| CVE-2024-40774 |
A downgrade issue was addressed with additional code-signing restrictions
|
5.9
Medium
|
Jul 29, 2024 |
| CVE-2023-40398 |
This issue was addressed with improved checks
|
8.8
High
|
Jul 29, 2024 |
| CVE-2023-42957 |
A permissions issue was addressed with additional restrictions
|
3.3
Low
|
Jul 29, 2024 |
| CVE-2023-42925 |
The issue was addressed with improved restriction of data container access
|
3.3
Low
|
Jul 29, 2024 |
| CVE-2023-42949 |
This issue was addressed with improved data protection
|
3.3
Low
|
Jul 29, 2024 |
| CVE-2023-40396 |
The issue was addressed with improved memory handling
|
7.8
High
|
Jul 29, 2024 |
| CVE-2024-27851 |
The issue was addressed with improved bounds checks
|
7.5
High
|
Jun 10, 2024 |
| CVE-2024-27830 |
This issue was addressed through improved state management
|
6.5
Medium
|
Jun 10, 2024 |
| CVE-2024-27806 |
This issue was addressed with improved environment sanitization
|
5.5
Medium
|
Jun 10, 2024 |
| CVE-2024-27811 |
The issue was addressed with improved checks
|
9.1
Critical
|
Jun 10, 2024 |
| CVE-2024-27807 |
The issue was addressed with improved checks
|
4.3
Medium
|
Jun 10, 2024 |
| CVE-2024-27850 |
This issue was addressed with improvements to the noise injection algorithm
|
6.5
Medium
|
Jun 10, 2024 |
| CVE-2024-27831 |
An out-of-bounds write issue was addressed with improved input validation
|
7.5
High
|
Jun 10, 2024 |
| CVE-2024-27800 |
This issue was addressed by removing the vulnerable code
|
7.1
High
|
Jun 10, 2024 |
| CVE-2024-27857 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.1
High
|
Jun 10, 2024 |
| CVE-2024-27820 |
The issue was addressed with improved memory handling
|
7.5
High
|
Jun 10, 2024 |
| CVE-2024-27836 |
The issue was addressed with improved checks
|
7.8
High
|
Jun 10, 2024 |
| CVE-2024-27840 |
The issue was addressed with improved memory handling
|
7.5
High
|
Jun 10, 2024 |
| CVE-2024-27801 |
The issue was addressed with improved checks
|
8.4
High
|
Jun 10, 2024 |
| CVE-2024-27817 |
The issue was addressed with improved checks
|
7.8
High
|
Jun 10, 2024 |
| CVE-2024-27802 |
An out-of-bounds read was addressed with improved input validation
|
7.8
High
|
Jun 10, 2024 |