CVE-2022-32805
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 handling of caches. This issue is fixed in Security Update 2022-005 Catalina, macOS Big Sur 11.6.8, macOS Monterey 12.5. An app may be able to access sensitive user information.
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 confidenceCVE-2022-32805 is a macOS vulnerability stemming from improper cache handling that allows a local application to potentially access sensitive user information. The issue was addressed through improved cache management in the relevant macOS 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= 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Identify the installed macOS versionOpen Terminal and run: sw_vers -productVersionAffected if The version displayed is 10.15.7, or falls between 11.0 and 11.6.7, or falls between 12.0 and 12.4
-
Confirm the major version numberRun: sw_vers -productVersion | cut -d. -f1 to get the major version (10, 11, or 12)Affected if The major version is 10 (Catalina), 11 (Big Sur), or 12 (Monterey)
-
Check if the specific minor/patch version is in the affected rangeCompare the full version string from step 1 against: 10.15.7; 11.0 to 11.6.7; 12.0 to 12.4Affected if The installed version exactly matches 10.15.7, or is 11.0-11.6.7, or is 12.0-12.4
A user is affected if their macOS version is exactly 10.15.7, or between 11.0 and 11.6.7, or between 12.0 and 12.4; versions 11.6.8 and above or 12.5 and above are not affected.
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 security update for the macOS version in use: Security Update 2022-005 for Catalina, macOS 11.6.8 for Big Sur, or macOS 12.5 for Monterey.
macOS 10.15.7 with Security Update 2022-005, macOS Big Sur 11.6.8, or macOS Monterey 12.5 (or latest available)
- Identify the current macOS version by clicking the Apple menu and selecting About This Mac
- For macOS 10.15.7 (Catalina): Install Security Update 2022-005 by going to System Preferences > Software Update
- For macOS 11.x (Big Sur): Upgrade to macOS Big Sur 11.6.8 via System Preferences > Software Update
- For macOS 12.x (Monterey): Upgrade to macOS Monterey 12.5 via System Preferences > Software Update
- Alternatively, upgrade to the latest available macOS version for the device (currently macOS Ventura 13.x or later depending on hardware support)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32805 — 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-32805 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