| CVE-2024-54523 |
The issue was addressed with improved bounds checks
|
9.1
Critical
|
Jan 27, 2025 |
| CVE-2025-24096 |
This issue was addressed through improved state management
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54542 |
An authentication issue was addressed with improved state management
|
9.1
Critical
|
Jan 27, 2025 |
| CVE-2025-24106 |
This issue was addressed with additional entitlement checks
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54539 |
This issue was addressed through improved state management
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24146 |
This issue was addressed with improved redaction of sensitive information
|
9.8
Critical
|
Jan 27, 2025 |
| CVE-2025-24151 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24150 |
A privacy issue was addressed with improved handling of files
|
8.8
High
|
Jan 27, 2025 |
| CVE-2025-24107 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Jan 27, 2025 |
| CVE-2024-54543 |
The issue was addressed with improved memory handling
|
8.8
High
|
Jan 27, 2025 |
| CVE-2024-54522 |
The issue was addressed with improved bounds checks
|
7.8
High
|
Jan 27, 2025 |
| CVE-2024-54488 |
A logic issue was addressed with improved file handling
|
5.3
Medium
|
Jan 27, 2025 |
| CVE-2024-44172 |
A privacy issue was addressed with improved private data redaction for log entries
|
3.3
Low
|
Jan 27, 2025 |
| CVE-2025-24127 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54518 |
The issue was addressed with improved bounds checks
|
5.3
Medium
|
Jan 27, 2025 |
| CVE-2025-24131 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24086 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24100 |
A logic issue was addressed with improved restrictions
|
3.3
Low
|
Jan 27, 2025 |
| CVE-2025-24116 |
An access issue was addressed with additional sandbox restrictions
|
4.4
Medium
|
Jan 27, 2025 |
| CVE-2025-24161 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54509 |
An out-of-bounds write issue was addressed with improved input validation
|
7.8
High
|
Jan 27, 2025 |
| CVE-2025-24136 |
This issue was addressed with improved validation of symlinks
|
4.4
Medium
|
Jan 27, 2025 |
| CVE-2025-24120 |
This issue was addressed by improved management of object lifetimes
|
7.5
High
|
Jan 27, 2025 |
| CVE-2025-24177 |
A null pointer dereference was addressed with improved input validation
|
7.5
High
|
Jan 27, 2025 |
| CVE-2024-54499 |
A use-after-free issue was addressed with improved memory management
|
8.1
High
|
Jan 27, 2025 |