CVE-2021-1740
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 parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in Security Update 2021-002 Catalina, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5, macOS Big Sur 11.3. A local user 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 confidenceCVE-2021-1740 is a path validation vulnerability in Apple's file system path parsing logic. The flaw allowed a local authenticated user to manipulate directory paths to access protected areas of the file system that should be restricted. The fix implemented improved path validation to prevent directory traversal attacks.
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.15, <= 10.15.5= 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhone or iPadGo to Settings > General > About > Version, or run 'sw_vers' in terminalAffected if Version is less than 14.5 (e.g., 14.4.x, 14.3.x, etc.)
-
Check iPadOS versionGo to Settings > General > About > Version, or run 'sw_vers' in terminalAffected if Version is less than 14.5
-
Check macOS version on Catalina (10.15.x)Go to Apple menu > About This Mac, or run 'sw_vers' in terminalAffected if Version is 10.15, 10.15.1, 10.15.2, 10.15.3, 10.15.4, 10.15.5, 10.15.6, or 10.15.7
-
Check macOS version on Big Sur (11.x)Go to Apple menu > About This Mac, or run 'sw_vers' in terminalAffected if Version is 11.0, 11.1, or 11.2.x (11.2, 11.2.1, etc.)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via Xcode or Finder when connectedAffected if Version is less than 14.5
-
Check watchOS versionOpen the Watch app on paired iPhone, go to My Watch > General > About, or check in the Watch app under SettingsAffected if Version is less than 7.4
You are affected if your device runs any iOS/iPadOS, macOS, tvOS, or watchOS version listed in the affected ranges above, specifically versions below 14.5 for mobile platforms, 10.15.x for Catalina, or 11.0-11.2.x for Big Sur.
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 vendor patch: Security Update 2021-002 for Catalina, iOS 14.5/iPadOS 14.5, watchOS 7.4, tvOS 14.5, or macOS Big Sur 11.3 and later.
iOS/iPadOS 14.5, macOS Big Sur 11.3, Security Update 2021-002 for macOS Catalina, watchOS 7.4, tvOS 14.5
- Identify the current installed version of the affected Apple product (iOS, iPadOS, macOS, watchOS, or tvOS)
- Back up all important data before performing the update
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 14.5 or later
- For Mac: Go to System Preferences > Software Update and install macOS Big Sur 11.3 or later, or for Catalina apply Security Update 2021-002
- For Apple Watch: On the iPhone, open the Watch app, go to General > Software Update and install watchOS 7.4 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.5 or later
- Verify the update was successful by checking the software version after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1740 — 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-1740 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