| CVE-2024-27874 |
This issue was addressed through improved state management
|
7.5
Élevée
|
16 sept. 2024 |
| CVE-2024-44176 |
An out-of-bounds access issue was addressed with improved bounds checking
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-40791 |
A privacy issue was addressed with improved private data redaction for log entries
|
3.3
Faible
|
16 sept. 2024 |
| CVE-2024-40857 |
This issue was addressed through improved state management
|
6.1
Moyenne
|
16 sept. 2024 |
| CVE-2024-44183 |
A logic error was addressed with improved error handling
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-44171 |
This issue was addressed through improved state management
|
4.6
Moyenne
|
16 sept. 2024 |
| CVE-2024-44167 |
This issue was addressed by removing the vulnerable code
|
8.1
Élevée
|
16 sept. 2024 |
| CVE-2024-44184 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-40850 |
A file access issue was addressed with improved input validation
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-44147 |
This issue was addressed through improved state management
|
7.7
Élevée
|
16 sept. 2024 |
| CVE-2024-27869 |
The issue was addressed with improved checks
|
7.5
Élevée
|
16 sept. 2024 |
| CVE-2024-44202 |
An authentication issue was addressed with improved state management
|
5.3
Moyenne
|
16 sept. 2024 |
| CVE-2024-40826 |
A privacy issue was addressed with improved handling of files
|
6.1
Moyenne
|
16 sept. 2024 |
| CVE-2024-44131 |
This issue was addressed with improved validation of symlinks
|
5.5
Moyenne
|
16 sept. 2024 |
| CVE-2024-44127 |
This issue was addressed through improved state management
|
5.3
Moyenne
|
16 sept. 2024 |
| CVE-2024-40830 |
This issue was addressed with improved data protection
|
3.3
Faible
|
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-40798 |
This issue was addressed with improved redaction of sensitive information
|
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-27871 |
A path handling issue was addressed with improved validation
|
5.5
Moyenne
|
29 juil. 2024 |
| CVE-2024-27826 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
29 juil. 2024 |
| CVE-2024-40794 |
This issue was addressed through improved state management
|
5.3
Moyenne
|
29 juil. 2024 |
| CVE-2024-40833 |
A logic issue was addressed with improved checks
|
6.2
Moyenne
|
29 juil. 2024 |
| CVE-2024-27884 |
This issue was addressed with a new entitlement
|
5.5
Moyenne
|
29 juil. 2024 |