CVE-2021-30705
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 tvOS 14.6, 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. Processing a maliciously crafted ASTC file may disclose memory contents.
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 memory disclosure vulnerability in Apple's ASTC texture file parser allows processing of maliciously crafted ASTC files to leak adjacent memory contents. The issue stems from insufficient bounds checking during ASTC texture parsing, enabling an information disclosure attack.
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.6< 14.6>= 10.14, <= 10.14.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7>= 11.0, < 11.4< 14.6< 7.5CVSS 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 system and versionOn macOS, run 'sw_vers' or check System Preferences > About. On iOS/iPadOS, go to Settings > General > About. On tvOS/watchOS, check in Settings > General > About.Affected if The OS version cannot be determined or is not an Apple platform
-
Determine if macOS is affectedIf running macOS, compare the installed version (from sw_vers) against these ranges: 10.14.x where x <= 5, 10.14.6, 10.15.x where x <= 6, 10.15.7, or 11.0 to 11.3Affected if The macOS version falls within 10.14.0-10.14.5, 10.14.6, 10.15.0-10.15.6, 10.15.7, or 11.0-11.3
-
Determine if iOS or iPadOS is affectedIf running iOS or iPadOS, compare the installed version (from Settings > General > About) against the affected range of versions earlier than 14.6Affected if The iOS or iPadOS version is earlier than 14.6 (e.g., 14.5.x, 13.x, etc.)
-
Determine if tvOS or watchOS is affectedIf running tvOS or watchOS, compare the installed version against the affected range of versions earlier than 14.6 (tvOS) or earlier than 7.5 (watchOS)Affected if The tvOS version is earlier than 14.6 or the watchOS version is earlier than 7.5
The environment is affected if any Apple device runs an OS version that falls within the specified vulnerable ranges for iOS, iPadOS, macOS, tvOS, or watchOS.
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.511.414.6
Apply the vendor-supplied security updates for the affected Apple operating systems (iOS 14.6+, iPadOS 14.6+, macOS Big Sur 11.4+, tvOS 14.6+, watchOS 7.5+, or the specific Security Updates 2021-003/004 for older macOS) to address the improper input validation in the ASTC parser.
iOS 14.6 / iPadOS 14.6 / macOS Big Sur 11.4 / tvOS 14.6 / watchOS 7.5 / Security Update 2021-004 Mojave / Security Update 2021-003 Catalina
- For iOS devices: Go to Settings > General > Software Update and install iOS 14.6
- For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 14.6
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.4
- For macOS Mojave (10.14.x): Go to System Preferences > Software Update and install Security Update 2021-004 Mojave
- For macOS Catalina (10.15.x): Go to System Preferences > Software Update and install Security Update 2021-003 Catalina
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.6
- For Apple Watch: Go to Settings > General > Software Update and install watchOS 7.5
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30705 — 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-30705 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