CVE-2022-42866 json
The issue was addressed with improved handling of caches.
published 2022-12-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-45929
- cvss
- 5.5
- 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 27%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved handling of caches. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, watchOS 9.2. An app may be able to read sensitive location information.
Patch / fix
- Apple tvOS 13.1, 16.2
- Apple watchOS 9.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/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:N/UI:R/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected products
- Apple tvOS
- Apple watchOS
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
support.apple.com
/en-us/HT213535
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213532
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213530
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213536
release-notes, vendor-advisory
-
seclists.org
/fulldisclosure/2022/Dec/20
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Dec/23
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Dec/26
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Dec/27
mailing-list, third-party-advisory
Sources
- CVE List CVE-2022-42866
- NVD CVE-2022-42866
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.