dbcve.org
Mac Os XOperating system · Apple

CVE-2022-32800

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 10.15.7 / 11.6.8 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
This issue was addressed with improved checks. 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 modify protected parts of the file system.

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 confidence

A vulnerability in macOS allowed an application to modify protected parts of the file system, bypassing filesystem protection mechanisms. Apple addressed this with improved checks in Security Update 2022-005 for Catalina, macOS Big Sur 11.6.8, and macOS Monterey 12.5.

MitigationApply the appropriate macOS security update (Security Update 2022-005 for Catalina, macOS Big Sur 11.6.8, or macOS Monterey 12.5 or later) to affected systems.

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
Mac Os XOperating system
Affected:= 10.15.7
macOSOperating system
Affected:< 10.15.7>= 11.0, < 11.6.8>= 12.0, < 12.5= 10.15.7

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed macOS version
    Click the Apple menu, select About This Mac, and note the version number under the macOS name
    Affected if The version shows 10.15.7, 11.0 through 11.6.7, or 12.0 through 12.4 (these are the affected versions)
  2. Confirm patch installation status
    Open System Preferences (System Settings on Monterey), go to Software Update, and check if any Security Update 2022-005 is listed as installed
    Affected if No security update is installed on an affected macOS version (10.15.7, 11.x before 11.6.8, or 12.x before 12.5)

You are affected if your macOS version is 10.15.7, 11.0-11.6.7, or 12.0-12.4 and Security Update 2022-005 has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.15.7 / 11.6.8 / 12.5 or later
Fixed in 10.15.711.6.812.5
Interim mitigation

Apply the appropriate macOS security update (Security Update 2022-005 for Catalina, macOS Big Sur 11.6.8, or macOS Monterey 12.5 or later) to affected systems.

Recommended fix High confidence

Security Update 2022-005 Catalina, macOS Big Sur 11.6.8, or macOS Monterey 12.5 (depending on your current macOS version)

  1. 1. Determine the current macOS version by clicking the Apple menu and selecting 'About This Mac'
  2. 2. For macOS 10.15.7 (Catalina): Apply Security Update 2022-005 Catalina via System Preferences > Software Update
  3. 3. For macOS 11.x (Big Sur): Upgrade to macOS Big Sur 11.6.8 via System Preferences > Software Update
  4. 4. For macOS 12.x (Monterey): Upgrade to macOS Monterey 12.5 via System Preferences > Software Update
  5. 5. After updating, restart the system as prompted
  6. 6. Verify the update was applied by checking System Preferences > Software Update again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32800 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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