IpadosOperating system · Apple

CVE-2022-42801

HIGH · 7.8 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 5.7.1 / 9.1 or later.
See remediation →
81/100
Remediation priority · High
Public exploit No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpadosOperating system
Affected:< 5.7.1
Iphone OsOperating system
Affected:< 5.7.1
macOSOperating system
Affected:>= 12.0, < 12.6.1
TvosOperating system
Affected:< 16.1
WatchosOperating system
Affected:< 9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.7.1 / 9.1 / 12.6.1 or later
Fixed in 5.7.19.112.6.1
Recommended fix High confidence

iOS 15.7.1+/iPadOS 15.7.1+, macOS Monterey 12.6.1/macOS Ventura 13, tvOS 16.1, watchOS 9.1

  1. For iPhone/iPad: Upgrade to iOS 15.7.1 or later (or iOS 16.1+/iPadOS 15.7.1+/iPadOS 16+ for newer features) via Settings > General > Software Update
  2. For macOS Monterey (12.x): Upgrade to macOS Monterey 12.6.1 via System Preferences > Software Update
  3. For macOS Ventura (13.x): Upgrade to macOS Ventura 13 via System Preferences > Software Update
  4. For Apple TV: Upgrade to tvOS 16.1 via Settings > System > Software Updates
  5. For Apple Watch: Upgrade to watchOS 9.1 via the Watch app on iPhone > General > Software Update
Caveat Upgrades may include significant OS changes; ensure backup before updating and verify app compatibility with newer iOS/macOS versions

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42801 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data