CVE-2021-30855
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 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-005 Catalina, iOS 14.8 and iPadOS 14.8, iOS 15 and iPadOS 15, watchOS 8, macOS Big Sur 11.6. 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 confidenceA validation issue existed in the handling of symlinks in multiple Apple operating systems (macOS, iOS, iPadOS, and watchOS). The improper validation allowed an application to traverse symlinks and access restricted files outside the intended directory boundaries, potentially bypassing sandbox restrictions.
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.8< 14.8< 10.15.7= 10.15.7< 11.6< 15.0< 8.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the operating systemRun 'sw_vers' on macOS, or check Settings > General > About on iOS/iPadOS/watchOS/tvOS to determine the product name and exact version numberAffected if The device runs any of: iPadOS, iPhone OS, macOS, tvOS, or watchOS - proceed to version check
-
Check macOS versionRun 'sw_vers -productVersion' or 'system_profiler SPSoftwareDataType' to get the exact macOS build versionAffected if Version is 10.15.7 (any build) OR less than 10.15.7 OR less than 11.6 (for macOS Big Sur)
-
Check iOS/iPadOS versionCheck Settings > General > About > Version on the device, or use Xcode or device management tools to query the iOS versionAffected if Version is less than 14.8
-
Check watchOS versionCheck the Watch app on paired iPhone > My Watch > General > About, or check directly on the watch in Settings > General > AboutAffected if Version is less than 8.0
-
Check tvOS versionCheck Settings > General > About > Version on Apple TV, or use Apple Configurator or device management toolsAffected if Version is less than 15.0
You are affected if your device runs any of: iPadOS/iOS < 14.8, macOS 10.15.7 (any build) or < 10.15.7, macOS < 11.6, watchOS < 8.0, or tvOS < 15.0 - the symlink validation flaw exists in these unpatched versions.
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 · scoped8.010.15.711.6
Apply the appropriate Apple security update for the affected product: Security Update 2021-005 for macOS Catalina, iOS 14.8/iPadOS 14.8, iOS 15/iPadOS 15, watchOS 8, or macOS Big Sur 11.6.
iOS/iPadOS 14.8 or later (or iOS 15+); macOS 11.6 or Security Update 2021-005 for Catalina 10.15.7; watchOS 8.0+; tvOS 15.0+
- 1. Identify the Apple device type (iPhone, iPad, Mac, Apple Watch, Apple TV)
- 2. Check the current installed OS version in Settings > General > About (iOS/iPadOS) or System Preferences > About (macOS)
- 3. For iPhone/iPad: Navigate to Settings > General > Software Update and upgrade to iOS/iPadOS 14.8 or later (iOS 15+ also contains the fix)
- 4. For Mac: Open System Preferences > Software Update and install Security Update 2021-005 Catalina, or upgrade to macOS Big Sur 11.6 or later
- 5. For Apple Watch: Install watchOS 8 via the Watch app on iPhone
- 6. For Apple TV: Install tvOS 15 via Settings > System > Software Updates
- 7. After updating, verify the OS version meets or exceeds the fixed versions: iOS/iPadOS 14.8+, macOS 11.6+, watchOS 8.0+, tvOS 15.0+
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30855 — 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-30855 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