CVE-2024-27828 json
The issue was addressed with improved memory handling.
published 2024-06-10 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-25021
- cvss
- 7.0
- 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 18%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved memory handling. This issue is fixed in iOS 17.5 and iPadOS 17.5, tvOS 17.5, visionOS 1.2, watchOS 10.5. An app may be able to execute arbitrary code with kernel privileges.
Patch / fix
- Apple iOS and iPadOS 17.5
- Apple tvOS 17.5
- Apple visionOS 1.2
- Apple watchOS 10.5
- apple iphone_os 17.5
- apple ipad_os 17.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Apple iOS and iPadOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
- apple iphone_os
- apple ipad_os
Classification
References
-
support.apple.com
/en-us/HT214101
vendor-advisory
-
support.apple.com
/en-us/HT214108
vendor-advisory
-
support.apple.com
/en-us/HT214104
vendor-advisory
-
support.apple.com
/en-us/HT214102
vendor-advisory
-
support.apple.com
/kb/HT214102
vendor-advisory
-
support.apple.com
/kb/HT214104
vendor-advisory
-
support.apple.com
/kb/HT214101
vendor-advisory
-
support.apple.com
/kb/HT214108
vendor-advisory
- support.apple.com /en-us/120901
- support.apple.com /en-us/120902
- support.apple.com /en-us/120905
- support.apple.com /en-us/120906
-
seclists.org
/fulldisclosure/2024/Jun/5
mailing-list, third-party-advisory
Sources
- CVE List CVE-2024-27828
- NVD CVE-2024-27828
Fencer Vulns 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.