CVE-2022-32947
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 iOS 16.1 and iPadOS 16, macOS Ventura 13, watchOS 9.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 · moderate confidenceA local application can exploit improper memory handling to execute arbitrary code with kernel privileges, achieving privilege escalation. This is a kernel-level memory corruption vulnerability fixed in Apple's 2022 security updates.
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.0< 16.1< 13.0< 9.1CVSS 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
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.
-
Identify the Apple device typeDetermine whether the device is an iPhone, iPad, Mac, or Apple Watch by checking the physical device or system informationAffected if Device is an Apple iPhone, iPad, Mac, or Apple Watch
-
Check iOS version on iPhoneOn iPhone, go to Settings > General > About and note the Version numberAffected if iOS version is below 16.1 (for example, 16.0.x or earlier)
-
Check iPadOS version on iPadOn iPad, go to Settings > General > About and note the Version numberAffected if iPadOS version is below 16.0 (for example, 15.x.x)
-
Check macOS version on MacOn Mac, go to System Settings > About or run 'sw_vers' in Terminal and note the version numberAffected if macOS version is below 13.0 (any version before Ventura)
-
Check watchOS version on Apple WatchOn Apple Watch, go to Settings > General > About and note the Version number, or check via the Watch app on paired iPhoneAffected if watchOS version is below 9.1
A device is affected if it is an Apple mobile device or computer running an OS version lower than the minimum patched release: iOS < 16.1, iPadOS < 16.0, macOS < 13.0, or watchOS < 9.1
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.113.016.0
Apply vendor-supplied patches (iOS 16.1+, iPadOS 16+, macOS Ventura 13+, watchOS 9.1+) to remediate this kernel-level privilege escalation vulnerability.
iOS 16.1, iPadOS 16, macOS Ventura 13, or watchOS 9.1 depending on device
- For iPhone: Go to Settings > General > Software Update and upgrade to iOS 16.1
- For iPad: Go to Settings > General > Software Update and upgrade to iPadOS 16
- For Mac: Go to System Settings > General > Software Update and upgrade to macOS Ventura 13
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and upgrade to watchOS 9.1
- After updating, verify the update was successful by checking the OS version in Settings/General/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32947 — 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-32947 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