| CVE-2025-24113 |
The issue was addressed with improved UI
|
4.3
Moyenne
|
27 janv. 2025 |
| CVE-2024-54535 |
A path handling issue was addressed with improved logic
|
4.0
Moyenne
|
15 janv. 2025 |
| CVE-2024-54470 |
A logic issue was addressed with improved checks
|
4.6
Moyenne
|
15 janv. 2025 |
| CVE-2024-40854 |
A memory initialization issue was addressed with improved memory handling
|
6.5
Moyenne
|
15 janv. 2025 |
| CVE-2024-40839 |
This issue was addressed through improved state management
|
2.4
Faible
|
15 janv. 2025 |
| CVE-2024-40771 |
The issue was addressed with improved memory handling
|
8.4
Élevée
|
15 janv. 2025 |
| CVE-2024-27856 |
The issue was addressed with improved checks
|
7.8
Élevée
|
15 janv. 2025 |
| CVE-2024-44136 |
This issue was addressed through improved state management
|
9.1
Critique
|
15 janv. 2025 |
| CVE-2024-54538 |
A denial-of-service issue was addressed with improved input validation
|
7.5
Élevée
|
20 déc. 2024 |
| CVE-2024-44299 |
The issue was addressed with improved bounds checks
|
8.8
Élevée
|
11 déc. 2024 |
| CVE-2024-54503 |
An inconsistent user interface issue was addressed with improved state management
|
3.3
Faible
|
11 déc. 2024 |
| CVE-2024-44201 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
11 déc. 2024 |
| CVE-2024-54485 |
The issue was addressed by adding additional logic
|
5.5
Moyenne
|
11 déc. 2024 |
| CVE-2024-44200 |
This issue was addressed with improved redaction of sensitive information
|
5.5
Moyenne
|
11 déc. 2024 |
| CVE-2024-54492 |
This issue was addressed by using HTTPS when sending information over the network
|
9.8
Critique
|
11 déc. 2024 |
| CVE-2024-44241 |
The issue was addressed with improved bounds checks
|
9.8
Critique
|
11 déc. 2024 |
| CVE-2024-54514 |
The issue was addressed with improved checks
|
8.2
Élevée
|
11 déc. 2024 |
| CVE-2024-54502 |
The issue was addressed with improved checks
|
6.5
Moyenne
|
11 déc. 2024 |
| CVE-2024-54534 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
11 déc. 2024 |
| CVE-2024-54505 |
A type confusion issue was addressed with improved memory handling
|
8.8
Élevée
|
11 déc. 2024 |
| CVE-2024-54513 |
A permissions issue was addressed with additional restrictions
|
5.7
Moyenne
|
11 déc. 2024 |
| CVE-2024-44246 |
The issue was addressed with improved routing of Safari-originated requests
|
4.3
Moyenne
|
11 déc. 2024 |
| CVE-2024-54508 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
11 déc. 2024 |
| CVE-2024-54494 |
A race condition was addressed with additional validation
|
5.9
Moyenne
|
11 déc. 2024 |
| CVE-2024-54527 |
This issue was addressed with improved checks
|
5.5
Moyenne
|
11 déc. 2024 |