CVE-2021-30843
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 · uneditedThis issue was addressed with improved checks. This issue is fixed in iOS 14.8 and iPadOS 14.8, macOS Big Sur 11.6, Security Update 2021-005 Catalina, tvOS 15, iOS 15 and iPadOS 15, watchOS 8. Processing a maliciously crafted dfont file may lead to arbitrary code execution.
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 confidenceA vulnerability in Apple CoreText font parsing logic allows arbitrary code execution when processing a maliciously crafted dfont (data font) file. The vulnerability stems from insufficient validation checks during dfont file processing, enabling a specially crafted file to trigger memory corruption and execute arbitrary code in the context of the parsing application.
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, <= 10.15.6= 10.15.7>= 11.0, < 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS/iPadOS versionGo to Settings > General > About > Version on iPhone or iPad. Compare the version number to the affected ranges: < 14.8 for iPadOS and iOS.Affected if The installed iOS or iPadOS version is lower than 14.8
-
Check macOS versionClick Apple menu > About This Mac. Compare the macOS version to affected ranges: 10.15.0 through 10.15.6, 10.15.7, or 11.0 through 11.5.x.Affected if The installed macOS version is 10.15.x (excluding 10.15.7+, which is patched), or 11.0-11.5.x
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV. Compare to affected range: < 15.0.Affected if The installed tvOS version is lower than 15.0
-
Check watchOS versionOpen the Watch app on iPhone, go to General > About > Watch Version. Compare to affected range: < 8.0.Affected if The installed watchOS version is lower than 8.0
-
Identify font processing activityReview installed applications that handle font files, particularly dfont files. Check if any applications automatically process fonts from untrusted sources or email attachments.Affected if Applications that parse dfont files using CoreText are in regular use, and the OS version falls within the affected ranges above
A user is affected if their device runs any iOS/iPadOS < 14.8, macOS 10.15.x (except 10.15.7+), macOS 11.0-11.5.x, tvOS < 15.0, or watchOS < 8.0, and they process dfont files through applications that use CoreText font parsing.
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.011.614.8
Apply vendor patches by updating affected devices to iOS 14.8+/15+, iPadOS 14.8+/15+, macOS Big Sur 11.6+/Security Update 2021-005+, tvOS 15+, or watchOS 8+ as appropriate. Implement file-type restrictions and disable automatic font loading from untrusted sources as a defense-in-depth measure.
iOS 14.8 / iPadOS 14.8 / macOS Big Sur 11.6 / Security Update 2021-005 Catalina / tvOS 15 / iOS 15 / iPadOS 15 / watchOS 8
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 14.8 or iPadOS 14.8 (or iOS 15/iPadOS 15 if desired)
- For macOS: Go to System Preferences > Software Update and install macOS Big Sur 11.6 (or Security Update 2021-005 for Catalina 10.15.7)
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 15
- For Apple Watch: Go to the Watch app on iPhone > My Watch > General > Software Update and install watchOS 8
- Ensure the device is connected to Wi-Fi and power during the update process
- Back up important data before performing major version upgrades (iOS 15, iPadOS 15, tvOS 15, watchOS 8)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30843 — 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-30843 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