CVE-2022-42842
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 · uneditedThe issue was addressed with improved memory handling. This issue is fixed in tvOS 16.2, macOS Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. A remote user may be able to cause kernel code execution.
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 · moderate confidenceThis is a kernel-level memory handling vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, watchOS, tvOS) that allows a remote attacker to potentially execute arbitrary code in the kernel context. The vulnerability was addressed with improved memory handling, suggesting a memory corruption issue such as a buffer overflow or use-after-free.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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< 16.2< 16.2>= 11.0, < 11.7.2>= 12.0.0, < 12.6.2= 13.0< 16.2< 9.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneOpen Settings > General > About on the iPhone device and look at the 'Version' fieldAffected if The version shown is less than 16.2 (for example, 16.1.x, 16.0.x, 15.x, etc.)
-
Check iPadOS version on iPadOpen Settings > General > About on the iPad device and look at the 'Version' fieldAffected if The version shown is less than 16.2 (for example, 16.1.x, 16.0.x, 15.x, etc.)
-
Check macOS versionClick the Apple menu > About This Mac. The version number is displayed under the macOS name (for example, 13.0, 12.6.1, 11.7.1)Affected if The version is 11.0 through 11.7.1, 12.0 through 12.6.1, or exactly 13.0 (not 13.1 or higher)
-
Check watchOS versionOpen the Settings app on Apple Watch, then go to General > About and note the watchOS version; or open the Watch app on iPhone and go to My Watch > General > AboutAffected if The version is less than 9.2 (for example, 9.1.x, 9.0.x, 8.x, etc.)
-
Check tvOS versionOpen Settings > General > About on Apple TV and note the version numberAffected if The version is less than 16.2 (for example, 16.1.x, 16.0.x, 15.x, etc.)
A device is affected if it is running any version of iOS, iPadOS, macOS, watchOS, or tvOS that falls below the patched version numbers (16.2 for iOS/iPadOS/watchOS/tvOS, 11.7.2/12.6.2/13.1 for macOS).
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.211.7.212.6.2
Apply the available security updates: iOS 16.2/iPadOS 16.2, macOS Monterey 12.6.2/macOS Ventura 13.1/macOS Big Sur 11.7.2, watchOS 9.2, and tvOS 16.2. Given the critical severity and kernel-level code execution capability, prioritize patching for any affected systems exposed to untrusted network inputs.
iOS 16.2 / iPadOS 16.2 / macOS Big Sur 11.7.2 / macOS Monterey 12.6.2 / macOS Ventura 13.1 / tvOS 16.2 / watchOS 9.2
- Identify the Apple device type (iPhone, iPad, Mac, Apple TV, or Apple Watch) and current operating system version via Settings > General > About or System Preferences > General > About
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 16.2 or iPadOS 16.2
- For Mac: Open System Preferences > Software Update and install the appropriate update: macOS Big Sur 11.7.2, macOS Monterey 12.6.2, or macOS Ventura 13.1
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 16.2
- For Apple Watch: On the iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 9.2
- Verify the update was successfully installed by checking the operating system version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42842 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-42842 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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