CVE-2021-1868
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 logic issue was addressed with improved state management. This issue is fixed in Security Update 2021-002 Catalina, Security Update 2021-003 Mojave, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5, macOS Big Sur 11.3. A local attacker may be able to elevate their privileges.
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 local privilege escalation vulnerability in multiple Apple operating systems (macOS, iOS/iPadOS, watchOS, tvOS). The flaw is a logic issue in state management that allows a local attacker with low-level access to elevate their privileges to higher (potentially root/administrator) levels. The fix involves improved state management within the affected components.
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.5< 14.5>= 10.14, <= 10.14.5>= 10.15, <= 10.15.5= 10.14.6= 10.15.6= 10.15.7>= 11.0, < 11.3< 14.5< 7.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Check macOS versionOpen Terminal and run: sw_vers -productVersionAffected if The version is 10.14.x (through 10.14.5 or exactly 10.14.6), 10.15.x (through 10.15.5, or exactly 10.15.6 or 10.15.7), or 11.0 through 11.2.x (any version below 11.3)
-
Check iOS/iPadOS versionGo to Settings > General > About on the device and note the version numberAffected if The version is any release earlier than 14.5 (for example, 14.4.x, 14.3.x, etc.)
-
Check watchOS versionOpen the Watch app on paired iPhone, go to My Watch > General > About and note the versionAffected if The version is any release earlier than 7.4
-
Check tvOS versionGo to Settings > General > About > Version on Apple TVAffected if The version is any release earlier than 14.5
-
Verify patch status via system updateOn macOS: System Preferences > Software Update. On iOS: Settings > General > Software Update. Confirm if updates are available or if the system reports being up to date.Affected if The system reports being up to date at a version still listed in the affected ranges, meaning the security update has not been applied
You are affected if any Apple device runs an OS version that falls within the vulnerable ranges listed (all versions below 14.5 for iOS/iPadOS/watchOS/tvOS, or the specific macOS versions 10.14.x, 10.15.x, and 11.0-11.2.x), and the corresponding security update has not been installed.
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.411.314.5
Apply the relevant security updates: Security Update 2021-002 for Catalina, Security Update 2021-003 for Mojave, macOS Big Sur 11.3, iOS 14.5/iPadOS 14.5, watchOS 7.4, and tvOS 14.5. Prioritize systems with direct user access or multi-user environments.
iOS 14.5 / iPadOS 14.5 / watchOS 7.4 / tvOS 14.5 / macOS 11.3 / Security Update 2021-002 Catalina / Security Update 2021-003 Mojave
- For iOS devices: Go to Settings > General > Software Update and install iOS 14.5 or later
- For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 14.5 or later
- For Apple Watch: On your iPhone, open the Watch app and go to My Watch > General > Software Update to install watchOS 7.4 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.5 or later
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS 11.3 or later
- For macOS Catalina (10.15): Install Security Update 2021-002 Catalina via System Preferences > Software Update
- For macOS Mojave (10.14): Install Security Update 2021-003 Mojave via System Preferences > Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1868 — 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-1868 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