CVE-2021-30849
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 · uneditedMultiple memory corruption issues were addressed with improved memory handling. This issue is fixed in iOS 14.8 and iPadOS 14.8, watchOS 8, Safari 15, tvOS 15, iOS 15 and iPadOS 15, iTunes 12.12 for Windows. Processing maliciously crafted web content 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 confidenceThis is a WebKit memory corruption vulnerability affecting iOS, iPadOS, watchOS, Safari, tvOS, and iTunes for Windows. Processing maliciously crafted web content triggers memory corruption issues (likely use-after-free, heap overflow, or similar), enabling arbitrary code execution with the privileges of the browser process.
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< 15.0< 12.12< 14.8< 14.8< 12.0.1< 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 Safari version on macOSOpen Safari > About Safari or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in TerminalAffected if Version is lower than 15.0 on macOS systems that browse the web
-
Check iOS or iPadOS versionGo to Settings > General > About on the device, or check via Apple Configurator, MDM, or device management consoleAffected if Version is lower than 14.8 on iPhones or iPads that use Safari or any app with WebView
-
Check watchOS versionOpen the Watch app on paired iPhone > My Watch > General > About, or check via MDMAffected if Version is lower than 8.0 on Apple Watch devices with browser or web-based functionality
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via MDMAffected if Version is lower than 15.0 on Apple TV devices using Safari app
-
Check iTunes version on WindowsOpen iTunes > Help > About iTunes, or check via 'C:\Program Files\iTunes\iTunes.exe' properties version infoAffected if Version is lower than 12.12 on Windows systems with iTunes installed
The environment is affected if any Apple device or software listed runs a version lower than the patched release (Safari 15+, iOS/iPadOS 14.8+, watchOS 8+, tvOS 15+, iTunes 12.12+, macOS 12.0.1+) and uses WebKit to render untrusted web content.
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.012.0.112.12
Apply the vendor-supplied patches: update to iOS/iPadOS 14.8 or 15, watchOS 8, Safari 15, tvOS 15, or iTunes 12.12 for Windows. For enterprises, ensure MDM-managed devices receive the updates and internal apps using WebView are tested for compatibility.
iOS 14.8/iPadOS 14.8, iOS 15/iPadOS 15, macOS 12.0.1 (Monterey), Safari 15, watchOS 8, tvOS 15, iTunes 12.12 for Windows
- For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS 14.8 or iOS 15
- For macOS: Go to System Preferences > Software Update and upgrade to macOS 12.0.1 (Monterey) or later
- For Safari: Update via macOS 12.0.1 or later, or download Safari 15 from Apple
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and upgrade to watchOS 8
- For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 15
- For iTunes (Windows): Download and install iTunes 12.12 for Windows from Apple
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30849 — 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-30849 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