CVE-2021-1849
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 · uneditedAn issue in code signature validation was addressed with improved checks. This issue is fixed in macOS Big Sur 11.3, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5. A malicious application may be able to bypass Privacy preferences.
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 code signature validation flaw in macOS/iOS/tvOS/watchOS allowed malicious applications to bypass Privacy preferences by exploiting insufficient validation checks in the code signature verification process, potentially enabling unauthorized access to sensitive user data or system resources.
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>= 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 your Apple operating system productDetermine which Apple platform your device runs: macOS (Mac computers), iOS (iPhone), iPadOS (iPad), tvOS (Apple TV), or watchOS (Apple Watch). This is typically visible in System Preferences > About or Settings > General > About.Affected if The device runs any of the affected Apple platforms (macOS, iOS, iPadOS, tvOS, or watchOS).
-
Check macOS version on Mac computersOpen Terminal and run: sw_vers -productVersion. Alternatively, go to Apple menu > About This Mac to view the macOS version number.Affected if The installed macOS version is 11.0 through 11.2.x (any version >= 11.0 but < 11.3). Versions 11.3 and later are not affected.
-
Check iOS version on iPhoneOpen Settings > General > About and look at the 'Version' field. Alternatively, connect to a computer with iTunes/Finder and check the device summary.Affected if The installed iOS version is any version < 14.5 (including 14.4.x, 14.3.x, 14.2.x, 14.1.x, 14.0.x, and earlier).
-
Check iPadOS version on iPadOpen Settings > General > About and look at the 'Version' field.Affected if The installed iPadOS version is any version < 14.5.
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV device.Affected if The installed tvOS version is any version < 14.5.
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About, and check the watchOS version. Alternatively, check directly on the watch via Settings > General > About.Affected if The installed watchOS version is any version < 7.4.
You are affected if your device runs macOS 11.0-11.2.x, iOS/iPadOS < 14.5, tvOS < 14.5, or watchOS < 7.4, and if code signature validation is actively used by the system for application verification.
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 vendor-supplied patches: update to macOS Big Sur 11.3+, iOS 14.5+, iPadOS 14.5+, watchOS 7.4+, or tvOS 14.5+ to remediate this vulnerability.
iOS 14.5 / iPadOS 14.5 / macOS Big Sur 11.3 / tvOS 14.5 / watchOS 7.4
- Check current OS version on the device (Settings > General > About on iOS/iPadOS, System Preferences > About on macOS, Settings > General on tvOS/watchOS)
- Update to iOS 14.5 or later for iPhone devices
- Update to iPadOS 14.5 or later for iPad devices
- Update to macOS Big Sur 11.3 or later for Mac devices
- Update to tvOS 14.5 or later for Apple TV devices
- Update to watchOS 7.4 or later for Apple Watch devices
- Verify the update was successful by checking the OS version again
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-1849 — 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-1849 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