Mac Os XOperating system · Apple

CVE-2021-1784

HIGH · 7.5 CVSS v3.1 Published 2021-09-08
Fix available
A fix is available. Upgrade to 11.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 existed in DiskArbitration. This was addressed with additional ownership checks. This issue is fixed in macOS Big Sur 11.3, Security Update 2021-002 Catalina, Security Update 2021-003 Mojave. A malicious application 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 · high confidence

A permissions bypass vulnerability in macOS DiskArbitration framework allowed a malicious local application to modify protected parts of the file system due to missing ownership validation checks before disk operations.

MitigationApply the relevant macOS security update: macOS Big Sur 11.3, Security Update 2021-002 (Catalina), or Security Update 2021-003 (Mojave) depending on the installed OS version.

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.14, <= 10.14.5>= 10.15, <= 10.15.5= 10.14.6= 10.15.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.3

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
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 checks

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

  1. Determine installed macOS version
    Run 'sw_vers -productVersion' in Terminal, or go to Apple menu > About This Mac to view the version number
    Affected if The displayed version falls within the affected ranges: 10.14.x, 10.15.x, or 11.0-11.2.x
  2. Confirm full version number
    If running 10.14.x or 10.15.x, check the specific build version by running 'sw_vers -buildVersion' to confirm whether it matches the unpatched security update state
    Affected if The build version corresponds to an update level prior to the Security Update 2021-002 (Catalina) or Security Update 2021-003 (Mojave)
  3. Verify DiskArbitration framework availability
    The vulnerability exists in the DiskArbitration framework. Confirm the system has this framework by checking /System/Library/Frameworks/DiskArbitration.framework exists
    Affected if The framework is present (which it is by default on all affected macOS versions)

The environment is affected if the installed macOS version is 10.14 through 10.14.6, 10.15 through 10.15.7, or 11.0 through 11.2.x and the relevant security updates have 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 11.3 or later
Fixed in 11.3
Interim mitigation

Apply the relevant macOS security update: macOS Big Sur 11.3, Security Update 2021-002 (Catalina), or Security Update 2021-003 (Mojave) depending on the installed OS version.

Recommended fix High confidence

macOS Big Sur 11.3 or later, Security Update 2021-002 (Catalina), Security Update 2021-003 (Mojave)

  1. Identify current macOS version via Apple menu > About This Mac
  2. For macOS Big Sur (11.x) systems: Upgrade to macOS 11.3 or later via System Preferences > Software Update
  3. For macOS Catalina (10.15.x) systems: Apply Security Update 2021-002 via System Preferences > Software Update
  4. For macOS Mojave (10.14.x) systems: Apply Security Update 2021-003 via System Preferences > Software Update
  5. Verify the security update was successfully installed by checking System Preferences > Security & Privacy > General

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1784 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1784 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