dbcve.org
Mac Os XOperating system · Apple

CVE-2022-22583

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 10.15.7 / 11.6.3 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
A permissions issue was addressed with improved validation. This issue is fixed in Security Update 2022-001 Catalina, macOS Monterey 12.2, macOS Big Sur 11.6.3. An application may be able to access restricted files.

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

This is a permissions validation bypass vulnerability in macOS where an application could access restricted files due to insufficient permission validation checks. It allows a local application to circumvent file access restrictions that should be enforced by the operating system.

MitigationApply the appropriate macOS security update: Security Update 2022-001 for Catalina, macOS 12.2 for Monterey, or macOS 11.6.3 for Big Sur. This addresses the permissions validation issue that allowed restricted file 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
Mac Os XOperating system
Affected:>= 10.15, < 10.15.7= 10.15.7
macOSOperating system
Affected:< 11.6.3>= 12.0.0, < 12.3= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Identify the installed macOS version
    Run 'sw_vers -productVersion' in Terminal or go to Apple menu > About This Mac > Version
    Affected if The version displayed is 10.15.7, or less than 11.6.3, or between 12.0.0 and 12.2.x (inclusive)
  2. Confirm macOS build for additional precision
    Run 'sw_vers -buildVersion' to get the specific build number
    Affected if Build number corresponds to an unpatched version within the affected version ranges
  3. Verify if Security Update 2022-001 (Catalina) or equivalent is installed
    Check System Preferences > Security & Privacy > General for recent security updates, or run 'defaults read /Library/Preferences/com.apple.SoftwareUpdate.plist LastSuccessfulDate'
    Affected if No security update from early 2022 or later has been installed on macOS 10.15.x
  4. Check macOS 11.x (Big Sur) patch status
    Run 'system_profiler SPSoftwareDataType' to see installed system updates
    Affected if Running macOS 11.x without having installed the 11.6.3 security update
  5. Check macOS 12.x (Monterey) patch status
    Run 'softwareupdate -l' to list available updates or check System Preferences for installed updates
    Affected if Running macOS 12.0-12.2 without the 12.3 security update

You are affected if your macOS version is 10.15.7, any version of macOS 11.x prior to 11.6.3, or any version of macOS 12.x prior to 12.3, and the corresponding security update has not been installed.

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.3 / 12.3 or later
Fixed in 10.15.711.6.312.3
Interim mitigation

Apply the appropriate macOS security update: Security Update 2022-001 for Catalina, macOS 12.2 for Monterey, or macOS 11.6.3 for Big Sur. This addresses the permissions validation issue that allowed restricted file access.

Recommended fix High confidence

macOS 10.15: Security Update 2022-001 Catalina | macOS 11.x: 11.6.3 | macOS 12.x: 12.3

  1. Identify the current macOS version by clicking the Apple menu > About This Mac
  2. For macOS 10.15 (Catalina): Install Security Update 2022-001 Catalina via System Preferences > Software Update
  3. For macOS 11.x (Big Sur): Upgrade to macOS Big Sur 11.6.3 or later via System Preferences > Software Update
  4. For macOS 12.x (Monterey): Upgrade to macOS Monterey 12.3 or later via System Preferences > Software Update
  5. After upgrading, restart the system to apply the security update
  6. Verify the update was applied by checking System Preferences > About to confirm the version number
Caveat Standard macOS upgrade considerations apply - verify backup before upgrading, and ensure compatible applications

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

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22583 — 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-22583 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