CVE-2022-32812
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 macOS Monterey 12.5, macOS Big Sur 11.6.8, Security Update 2022-005 Catalina. 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 confidenceThis is a memory handling vulnerability in the macOS kernel that allows a locally installed application to escalate privileges and execute arbitrary code at the kernel level (ring 0). This is a privilege escalation vulnerability requiring local access.
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= 10.15.7< 10.15.7>= 11.0, < 11.6.8>= 12.0, < 12.5= 10.15.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
- 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.
-
Determine macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact version numberAffected if The version falls within the affected ranges: 10.15.7, 11.0 to 11.6.7, or 12.0 to 12.4
-
Check build number for additional precisionRun 'sw_vers -buildVersion' to get the build number, which can confirm the exact patch stateAffected if The build number is older than the patched builds for each version branch (for example, builds before 21G91 for Monterey 12.5)
-
Verify system is not receiving updatesCheck System Preferences > Software Update or run 'softwareupdate -l' to see if updates are availableAffected if No security updates are pending and the base version matches an affected release
A system is affected if it runs macOS Catalina 10.15.7, Big Sur 11.0-11.6.7, or Monterey 12.0-12.4 and has not applied the corresponding security update (2022-005, 11.6.8, or 12.5).
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 · scoped10.15.711.6.812.5
Apply the relevant macOS security updates: Monterey 12.5, Big Sur 11.6.8, or Security Update 2022-005 for Catalina, depending on the macOS version in use.
macOS Monterey 12.5, macOS Big Sur 11.6.8, or Security Update 2022-005 for Catalina (minimum)
- Identify the currently installed macOS version by clicking the Apple menu and selecting About This Mac
- For macOS Monterey (12.x) users: Go to System Preferences > Software Update and install macOS 12.5 or later
- For macOS Big Sur (11.x) users: Go to System Preferences > Software Update and install macOS 11.6.8 or later
- For macOS Catalina (10.15.7) users: Go to System Preferences > Software Update and install Security Update 2022-005 Catalina, or upgrade to a supported macOS version
- After updating, restart the system to apply the kernel-level security fix
- Verify the update was applied by checking System Preferences > Software Update for no remaining updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32812 — 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-32812 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