CVE-2021-30792
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 out-of-bounds write was addressed with improved input validation. This issue is fixed in iOS 14.7, macOS Big Sur 11.5. Processing a maliciously crafted image 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 confidenceAn out-of-bounds write vulnerability in the image processing components of iOS and macOS allows arbitrary code execution when a user processes a maliciously crafted image file. The vulnerability stems from insufficient input validation during image parsing.
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.7< 14.7>= 10.14.0, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7< 11.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
- 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 version on iPhoneOn iPhone, go to Settings > General > About and look at the 'Version' fieldAffected if Version number is less than 14.7 (for example, 14.6.1)
-
Check iPadOS version on iPadOn iPad, go to Settings > General > About and look at the 'Version' fieldAffected if Version number is less than 14.7 (for example, 14.6)
-
Check macOS version on MacOn Mac, click the Apple menu > About This Mac. The version number appears below the macOS nameAffected if Version is 10.14.0 through 10.14.6, 10.15 through 10.15.7, or any version below 11.5 (for example, 10.14.5, 10.15.6, 11.4)
A device is affected if it runs iOS/iPadOS below 14.7 or macOS below 11.5 (or in the 10.14.x/10.15.x ranges), and if users process untrusted image files with built-in image viewing or editing tools.
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 · scoped10.14.610.15.711.5
Update all affected iOS devices to version 14.7 or later and macOS Big Sur systems to version 11.5 or later to apply the patch.
iOS 14.7+, iPadOS 14.7+, macOS Big Sur 11.5+
- For iOS devices: Go to Settings > General > Software Update and install iOS 14.7 or later
- For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 14.7 or later
- For macOS devices: Go to System Preferences > Software Update (or System Settings > General > Software Update on newer macOS) and install macOS Big Sur 11.5 or later
- After updating, verify the update was successful by checking the OS version in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30792 — 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-30792 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