CVE-2022-42801 json
A logic issue was addressed with improved checks.
published 4y ago modified 4mo ago also EUVD-2022-45864
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
A logic issue was addressed with improved checks. This issue is fixed in tvOS 16.1, iOS 15.7.1 and iPadOS 15.7.1, macOS Ventura 13, watchOS 9.1, iOS 16.1 and iPadOS 16, macOS Monterey 12.6.1. An app may be able to execute arbitrary code with kernel privileges.
Patch / fix
- Apple macOS 13
- Apple tvOS 12.6, 15.7, 16.1
- Apple watchOS 9.1
Is CVE-2022-42801 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
- total
- Assessed
- last yr.
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 macOS
- Apple tvOS
- Apple watchOS
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
support.apple.com
/en-us/HT213488
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213494
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213489
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213492
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213491
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213490
release-notes, vendor-advisory
-
packetstormsecurity.com
/files/170011/XNU-vm_object-Use-After-Free.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-42801
- NVD CVE-2022-42801
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.