| CVE-2024-40850 |
A file access issue was addressed with improved input validation
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-44170 |
A privacy issue was addressed by moving sensitive data to a more secure location
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-40777 |
An out-of-bounds access issue was addressed with improved bounds checking
|
3.3
Faible
|
29 juil. 2024 |
| CVE-2024-40809 |
A logic issue was addressed with improved checks
|
7.8
Élevée
|
29 juil. 2024 |
| CVE-2024-27826 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
29 juil. 2024 |
| CVE-2024-27884 |
This issue was addressed with a new entitlement
|
5.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-40813 |
A lock screen issue was addressed with improved state management
|
4.6
Moyenne
|
29 juil. 2024 |
| CVE-2024-40805 |
A permissions issue was addressed with additional restrictions
|
7.7
Élevée
|
29 juil. 2024 |
| CVE-2024-40782 |
A use-after-free issue was addressed with improved memory management
|
9.8
Critique
|
29 juil. 2024 |
| CVE-2024-40829 |
The issue was addressed with improved checks
|
7.5
Élevée
|
29 juil. 2024 |
| CVE-2024-40812 |
A logic issue was addressed with improved checks
|
7.8
Élevée
|
29 juil. 2024 |
| CVE-2024-40795 |
This issue was addressed with improved data protection
|
3.3
Faible
|
29 juil. 2024 |
| CVE-2024-40824 |
This issue was addressed through improved state management
|
7.7
Élevée
|
29 juil. 2024 |
| CVE-2024-40776 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-40815 |
A race condition was addressed with additional validation
|
7.5
Élevée
|
29 juil. 2024 |
| CVE-2024-40799 |
An out-of-bounds read issue was addressed with improved input validation
|
7.1
Élevée
|
29 juil. 2024 |
| CVE-2024-40784 |
An integer overflow was addressed with improved input validation
|
7.8
Élevée
|
29 juil. 2024 |
| CVE-2024-40788 |
A type confusion issue was addressed with improved memory handling
|
6.2
Moyenne
|
29 juil. 2024 |
| CVE-2024-40835 |
A logic issue was addressed with improved checks
|
5.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-40822 |
This issue was addressed by restricting options offered on a locked device
|
2.4
Faible
|
29 juil. 2024 |
| CVE-2024-40789 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-40818 |
This issue was addressed by restricting options offered on a locked device
|
4.6
Moyenne
|
29 juil. 2024 |
| CVE-2024-40785 |
This issue was addressed with improved checks
|
6.1
Moyenne
|
29 juil. 2024 |
| CVE-2024-40793 |
This issue was addressed by removing the vulnerable code
|
5.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-27863 |
An information disclosure issue was addressed with improved private data redaction for log entries
|
5.5
Moyenne
|
29 juil. 2024 |