IpadosOperating system · Apple

CVE-2021-30681

HIGH · 7.8 CVSS v3.1 Published 2021-09-08
Fix available
A fix is available. Upgrade to 7.5 / 11.4 or later.
See remediation →
81/100
Remediation priority · High
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
A validation issue existed in the handling of symlinks. This issue was addressed with improved validation of symlinks. This issue is fixed in Security Update 2021-004 Mojave, iOS 14.6 and iPadOS 14.6, Security Update 2021-003 Catalina, macOS Big Sur 11.4, watchOS 7.5. A malicious application may be able to gain root 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 · high confidence

A validation vulnerability in symlink handling allows a malicious local application to escalate privileges to root. The flaw involves improper validation of symbolic links, which can be exploited to gain unauthorized elevated access.

MitigationApply the relevant Apple security update: Security Update 2021-004 for Mojave, Security Update 2021-003 for Catalina, macOS Big Sur 11.4, iOS/iPadOS 14.6, or watchOS 7.5 to patch the symlink validation flaw.

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
IpadosOperating system
Affected:< 14.6
Iphone OsOperating system
Affected:< 14.6
Mac Os XOperating system
Affected:>= 10.14, <= 10.14.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.4
WatchosOperating system
Affected:< 7.5

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

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

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

  1. Identify the macOS version
    Run 'sw_vers -productVersion' in Terminal or check System Preferences > About
    Affected if The version is 10.14.x and <= 10.14.6, OR 10.15.x and <= 10.15.7, OR 11.x and < 11.4
  2. Identify iOS or iPadOS version
    Go to Settings > General > About on the device and note the version number
    Affected if The version is less than 14.6
  3. Identify watchOS version
    Open the Watch app on the paired iPhone, go to My Watch > General > About
    Affected if The version is less than 7.5
  4. Confirm the vulnerable component is present
    This vulnerability is in the core symlink handling system component; if the OS version is vulnerable, the affected component is present by default
    Affected if The OS version matches any of the affected ranges listed in the CVE

A system is affected if it runs any macOS version 10.14 through 10.14.6, 10.15 through 10.15.7, or 11.0 through 11.3.x; or any iOS/iPadOS version below 14.6; or any watchOS version below 7.5.

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 7.5 / 11.4 / 14.6 or later
Fixed in 7.511.414.6
Interim mitigation

Apply the relevant Apple security update: Security Update 2021-004 for Mojave, Security Update 2021-003 for Catalina, macOS Big Sur 11.4, iOS/iPadOS 14.6, or watchOS 7.5 to patch the symlink validation flaw.

Recommended fix High confidence

iOS 14.6, iPadOS 14.6, macOS Big Sur 11.4, Security Update 2021-003 Catalina, Security Update 2021-004 Mojave, watchOS 7.5

  1. Identify the affected Apple device (iPhone, iPad, Mac, or Apple Watch)
  2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 14.6/iPadOS 14.6
  3. For Mac: Go to System Preferences > Software Update and install macOS Big Sur 11.4 or apply Security Update 2021-003 Catalina / Security Update 2021-004 Mojave as appropriate
  4. For Apple Watch: On the iPhone, open the Watch app, go to General > Software Update and install watchOS 7.5
  5. After updating, verify the device is running the fixed version

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

Fix this in Ipados 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-30681 — 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-30681 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