CVE-2021-1793
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 macOS Big Sur 11.2, Security Update 2021-001 Catalina, Security Update 2021-001 Mojave, watchOS 7.3, tvOS 14.4, iOS 14.4 and iPadOS 14.4. 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 · moderate confidenceA vulnerability in Apple's image processing framework allows arbitrary code execution when processing a maliciously crafted image file. The issue stemmed from insufficient validation checks during image parsing, likely allowing memory corruption that could be exploited to execute arbitrary code with the privileges of the viewing 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.4< 14.4>= 10.15, < 10.15.7= 10.15.7>= 11.0.1, < 11.2< 14.4< 7.3CVSS 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.
-
Identify the Apple device and operating systemOn Mac, run 'sw_vers' in Terminal. On iPhone/iPad, go to Settings > General > About. On Apple Watch, use the Watch app on paired iPhone > General > About. On Apple TV, go to Settings > General > About.Affected if The device is an Apple product running one of the affected operating systems listed in the CVE.
-
Check the installed macOS versionRun 'sw_vers' on Mac and note the BuildVersion and ProductVersion. For macOS 10.15.x, note the exact minor version (e.g., 10.15.7). For macOS 11.x, note the minor version (e.g., 11.0.1, 11.1, 11.1).Affected if macOS 10.15.7 is installed, or macOS 10.15.x versions before 10.15.7, or macOS 11.0.1 through 11.1.x (versions below 11.2).
-
Check the installed iOS or iPadOS versionOn the device, go to Settings > General > About and note the version number (e.g., 14.3, 14.3.1).Affected if iOS or iPadOS versions below 14.4 are installed.
-
Check the installed watchOS versionOpen the Watch app on the paired iPhone, select your watch, go to General > About, and note the version. Alternatively, on Apple Watch go to Settings > General > About.Affected if watchOS versions below 7.3 are installed.
-
Check the installed tvOS versionOn Apple TV, go to Settings > General > About and note the tvOS version number.Affected if tvOS versions below 14.4 are installed.
-
Determine image processing exposureThe vulnerability is triggered when the system processes a maliciously crafted image file. Any application that parses image files (Preview, Safari, Photos, third-party apps) could trigger the flaw. No specific configuration change is required for exploitation; the issue is in the underlying image parsing framework.Affected if The affected OS version is running and the device has the capability to open or preview image files from any source.
The environment is affected if any Apple device is running an OS version lower than 14.4 for iOS/iPadOS/tvOS/watchOS, macOS 10.15.7 or earlier 10.15.x, or macOS 11.0.1 through 11.1.x.
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.
From vendor data7.310.15.711.2
Apply the relevant Apple security update (macOS Big Sur 11.2+/Security Update 2021-001, watchOS 7.3, tvOS 14.4, iOS/iPadOS 14.4) to all affected devices. Prioritize devices that process untrusted image content from external sources.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1793 — 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-1793 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