CVE-2023-42848 json
The issue was addressed with improved bounds checks.
published 2024-02-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-47269
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved bounds checks. This issue is fixed in watchOS 10.1, macOS Sonoma 14.1, tvOS 17.1, iOS 16.7.2 and iPadOS 16.7.2, iOS 17.1 and iPadOS 17.1, macOS Ventura 13.6.1. Processing a maliciously crafted image may lead to heap corruption.
Patch / fix
- Apple iOS and iPadOS 16.7, 17.1
- Apple tvOS 17.1
- Apple macOS 13.6, 13.6.1, 14.1
- Apple watchOS 10.1
- apple iphone_os 16.7, 17.1
- apple ipad_os 16.7, 17.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/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.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Apple iOS and iPadOS
- Apple tvOS
- Apple macOS
- Apple watchOS
- apple iphone_os
- apple ipad_os
Classification
References
-
support.apple.com
/en-us/HT213981
vendor-advisory
-
support.apple.com
/en-us/HT213987
vendor-advisory
-
support.apple.com
/en-us/HT213984
vendor-advisory
-
support.apple.com
/en-us/HT213988
vendor-advisory
-
support.apple.com
/en-us/HT213985
vendor-advisory
-
support.apple.com
/en-us/HT213982
vendor-advisory
- support.apple.com /kb/HT213988
- support.apple.com /kb/HT213984
- support.apple.com /kb/HT213982
Sources
- CVE List CVE-2023-42848
- NVD CVE-2023-42848
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.