CVE-2021-1782
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 race condition was addressed with improved locking. This issue is fixed in macOS Big Sur 11.2, Security Update 2021-001 Catalina, Security Update 2021-001 Mojave, watchOS 7.3, tvOS 14.4, iOS 14.4 and iPadOS 14.4. A malicious application may be able to elevate privileges. Apple is aware of a report that this issue may have been actively exploited..
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 confidenceThis is a race condition vulnerability in Apple's kernel/secure kernel that allows a malicious local application to elevate privileges to root or kernel level. The vulnerability was addressed with improved locking mechanisms. Apple publicly acknowledged this was being actively exploited in the wild as a zero-day.
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< 14.4< 14.4>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7>= 11.0, < 11.2< 14.4< 7.3CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Apple platform and OS versionOn macOS, run 'sw_vers' in Terminal. On iOS/iPadOS, go to Settings > General > About. On watchOS/tvOS, go to Settings > General > About. Note the exact version number displayed.Affected if The detected OS version falls into any of these vulnerable ranges: iOS < 14.4, iPadOS < 14.4, watchOS < 7.3, tvOS < 14.4, macOS 10.14.x before 10.14.6, macOS 10.15.x before 10.15.7, or macOS 11.0.x before 11.2.
-
Confirm macOS version on Mac computersRun 'system_profiler SPSoftwareDataType' or check Apple menu > About This Mac to verify the exact macOS version number.Affected if The reported version is 10.14, 10.14.1, 10.14.2, 10.14.3, 10.14.4, 10.14.5, 10.14.6, 10.15, 10.15.1, 10.15.2, 10.15.3, 10.15.4, 10.15.5, 10.15.6, 10.15.7, or any 11.0.x version below 11.2.
-
Verify iOS or iPadOS version on mobile devicesNavigate to Settings > General > About on the iPhone or iPad and record the Version field.Affected if The version shown is below 14.4 (for example, 14.3.x, 14.2.x, 13.x, etc.).
A device is affected if it runs any iOS, iPadOS, watchOS, tvOS, or macOS version lower than the fixed releases (iOS 14.4, iPadOS 14.4, watchOS 7.3, tvOS 14.4, macOS 10.14.6, macOS 10.15.7, or macOS 11.2).
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 · scoped7.310.14.610.15.7
Apply the appropriate Apple security update for the affected OS version (iOS 14.4, iPadOS 14.4, macOS 11.2/2021-001, watchOS 7.3, tvOS 14.4) to all managed devices. In enterprise environments, verify complete deployment across all endpoints.
iOS/iPadOS 14.4+, macOS 11.2+ (Big Sur), Security Update 2021-001 (Catalina/Mojave), watchOS 7.3+, tvOS 14.4+
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 14.4 or later
- For macOS: Go to System Preferences > Software Update and install the latest security update (macOS Big Sur 11.2, Security Update 2021-001 Catalina, or Security Update 2021-001 Mojave)
- For Apple Watch: On your iPhone, open the Watch app, go to General > Software Update, and install watchOS 7.3 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1782 — 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-2021-1782 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