CVE-2022-32847
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 · uneditedThis issue was addressed with improved checks. This issue is fixed in iOS 15.6 and iPadOS 15.6, macOS Big Sur 11.6.8, watchOS 8.7, tvOS 15.6, macOS Monterey 12.5, Security Update 2022-005 Catalina. A remote user may be able to cause unexpected system termination or corrupt kernel memory.
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 · high confidenceA remote attacker can exploit a kernel-level memory corruption vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, watchOS, tvOS) to cause system termination or corrupt kernel memory. The issue was addressed with improved bounds/validation checks in the kernel.
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< 15.6< 15.6= 10.15.7< 10.15.7>= 11.0, < 11.6.8>= 12.0, < 12.5= 10.15.7< 15.6< 8.7CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 your Apple operating systemDetermine whether the device runs iOS, iPadOS, macOS, watchOS, or tvOS. On macOS, run 'sw_vers' or click Apple menu > About This Mac. On iOS/iPadOS, go to Settings > General > About. On watchOS, go to Settings > General > About. On tvOS, go to Settings > General > About.Affected if The device runs any of the affected Apple operating systems listed in the CVE.
-
Check iOS or iPadOS versionOn iOS/iPadOS, go to Settings > General > About and note the version number (for example, 15.5 or 15.6). Compare against the affected range of versions less than 15.6.Affected if The installed iOS or iPadOS version is below 15.6 (for example, 15.5, 15.4, 15.3, etc.).
-
Check macOS versionOn macOS, click Apple menu > About This Mac or run 'sw_vers' in Terminal. Note the version number (for example, 12.4, 11.6.7, 10.15.7). Compare against the affected ranges: < 10.15.7; 10.15.7; >= 11.0 and < 11.6.8; >= 12.0 and < 12.5.Affected if The installed macOS version is 10.15.7, or less than 10.15.7, or between 11.0 and 11.6.7 inclusive, or between 12.0 and 12.4 inclusive.
-
Check watchOS versionOn Apple Watch, go to Settings > General > About and note the version number. Or pair with iPhone and check in the Watch app under General > About. Compare against the affected range of versions less than 8.7.Affected if The installed watchOS version is below 8.7 (for example, 8.6, 8.5, 8.4, etc.).
-
Check tvOS versionOn Apple TV, go to Settings > General > About TV and note the version number. Compare against the affected range of versions less than 15.6.Affected if The installed tvOS version is below 15.6 (for example, 15.5, 15.4, etc.).
The environment is affected if the installed iOS, iPadOS, macOS, watchOS, or tvOS version matches any of the specific version ranges listed as vulnerable in the CVE.
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 · scoped8.710.15.711.6.8
Apply the available security updates: iOS 15.6+, iPadOS 15.6+, macOS Big Sur 11.6.8+, macOS Monterey 12.5+, watchOS 8.7+, tvOS 15.6+, or Security Update 2022-005 for Catalina. Prioritize remote-facing devices and those with network exposure.
iOS 15.6/iPadOS 15.6, macOS Big Sur 11.6.8, macOS Monterey 12.5, Security Update 2022-005 Catalina, watchOS 8.7, tvOS 15.6 (depending on device)
- Identify the affected Apple device type (iPhone, iPad, Mac, Apple Watch, or Apple TV)
- Check the current operating system version on the device
- For iPhone or iPad: Upgrade to iOS 15.6 or iPadOS 15.6 or later
- For Mac running macOS Big Sur (11.x): Upgrade to macOS Big Sur 11.6.8 or later
- For Mac running macOS Monterey (12.x): Upgrade to macOS Monterey 12.5 or later
- For Mac running macOS Catalina (10.15.x): Apply Security Update 2022-005 Catalina
- For Apple Watch: Upgrade to watchOS 8.7 or later
- For Apple TV: Upgrade to tvOS 15.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32847 — 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-32847 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