CVE-2024-54513 json
A permissions issue was addressed with additional restrictions.
published last yr. modified 4mo ago also EUVD-2024-52611
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
A permissions issue was addressed with additional restrictions. This issue is fixed in iOS 18.2 and iPadOS 18.2, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2. An app may be able to access sensitive user data.
Patch / fix
- Apple iOS and iPadOS 18.2
- Apple macOS 15.2
- Apple tvOS 18.2
- Apple visionOS 2.2
- Apple watchOS 11.2
Is CVE-2024-54513 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
- last yr.
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.7 | CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-281 Improper Preservation of Permissions
References
-
support.apple.com
/en-us/121837
vendor-advisory
-
support.apple.com
/en-us/121839
vendor-advisory
-
support.apple.com
/en-us/121843
vendor-advisory
-
support.apple.com
/en-us/121844
vendor-advisory
-
support.apple.com
/en-us/121845
vendor-advisory
- seclists.org /fulldisclosure/2024/Dec/12
- seclists.org /fulldisclosure/2024/Dec/11
- seclists.org /fulldisclosure/2024/Dec/7
- seclists.org /fulldisclosure/2024/Dec/5
Sources
- CVE List CVE-2024-54513
- NVD CVE-2024-54513
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.