CVE-2024-40813 json
A lock screen issue was addressed with improved state management.
published 2y ago modified 4mo ago also EUVD-2024-38653
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
A lock screen issue was addressed with improved state management. This issue is fixed in iOS 17.6 and iPadOS 17.6, watchOS 10.6. An attacker with physical access may be able to use Siri to access sensitive user data.
Patch / fix
- Apple iOS and iPadOS 17.6
- Apple watchOS 10.6
Is CVE-2024-40813 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Apple iOS and iPadOS
- Apple watchOS
Classification
- Weakness
-
- CWE-922 Insecure Storage of Sensitive Information
References
-
support.apple.com
/en-us/HT214117
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT214124
release-notes, vendor-advisory
- support.apple.com /en-us/120909
- support.apple.com /en-us/120916
-
seclists.org
/fulldisclosure/2024/Jul/16
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2024/Jul/21
mailing-list, third-party-advisory
- support.apple.com /kb/HT214124
- support.apple.com /kb/HT214117
Sources
- CVE List CVE-2024-40813
- NVD CVE-2024-40813
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.