CVE-2022-42865 json
This issue was addressed by enabling hardened runtime.
published 3y ago modified 4mo ago also EUVD-2022-45928
- 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 24%
- public exploits
- 0
- none known
Summary
This issue was addressed by enabling hardened runtime. 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 bypass Privacy preferences.
Patch / fix
- Apple tvOS 13.1, 16.2
- Apple watchOS 9.2
Is CVE-2022-42865 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.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
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:N/I:H/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected products
- Apple tvOS
- Apple watchOS
Classification
- Weakness
-
- CWE-284 Improper Access Control
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
- support.apple.com /kb/HT213534
Sources
- CVE List CVE-2022-42865
- NVD CVE-2022-42865
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.