CVE-2022-32910
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 · uneditedA logic issue was addressed with improved checks. This issue is fixed in macOS Big Sur 11.6.8, macOS Monterey 12.5, Security Update 2022-005 Catalina. An archive may be able to bypass Gatekeeper.
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 confidenceThis is a logic vulnerability in macOS Gatekeeper that allows specially crafted archive files to bypass security checks and execute unsigned or untrusted code. The issue stems from insufficient validation of archive contents during the Gatekeeper inspection process.
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, < 10.15.7= 10.15.7>= 11.0, < 11.6.8>= 12.0, < 12.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 installed macOS versionOpen Terminal and run: sw_vers -productVersionAffected if Version is 10.15.x (any), 11.0-11.6.7, or 12.0-12.4 (these are the unpatched affected ranges)
-
Verify Gatekeeper statusRun: spctl --status in Terminal. Look for "assessment enabled" in the output.Affected if Gatekeeper is enabled (assessment enabled) - the bypass only affects systems with Gatekeeper active
-
Confirm if security update is appliedCheck System Preferences > Software Update, or run: defaults read /System/Library/CoreServices/CoreTypes.bundle/Contents/Info.plist SV_AppVersion 2>/dev/null to see if patched versions are runningAffected if System shows an unpatched version number from the affected ranges above
You are affected if running an unpatched macOS version (10.15.x, 11.0-11.6.7, or 12.0-12.4) with Gatekeeper enabled, as the vulnerability allows specially crafted archive files to bypass Gatekeeper's code signature validation.
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 appropriate Apple security update (macOS Big Sur 11.6.8, macOS Monterey 12.5, or Security Update 2022-005 Catalina) to affected systems to receive the improved Gatekeeper checks.
macOS Big Sur 11.6.8, macOS Monterey 12.5, or Security Update 2022-005 Catalina (depending on your baseline OS)
- Back up your Mac using Time Machine or another backup solution before performing any system update.
- Determine your current macOS version by clicking the Apple menu > About This Mac.
- For macOS 10.15 (Catalina): Install Security Update 2022-005 Catalina via System Preferences > Software Update.
- For macOS 11.x (Big Sur): Upgrade to macOS Big Sur 11.6.8 or later via System Preferences > Software Update.
- For macOS 12.x (Monterey): Upgrade to macOS Monterey 12.5 or later via System Preferences > Software Update.
- After the update completes, restart your Mac when prompted and verify the update was successful by checking About This Mac.
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-32910 — 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-32910 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