CVE-2021-30953
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 read was addressed with improved bounds checking. This issue is fixed in tvOS 15.2, macOS Monterey 12.1, Safari 15.2, iOS 15.2 and iPadOS 15.2, watchOS 8.3. 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 · high confidenceA memory safety vulnerability in WebKit (Apple's browser engine) allows an out-of-bounds read when processing maliciously crafted web content. The issue was addressed with improved bounds checking and affects Safari across multiple Apple platforms (iOS, iPadOS, macOS, tvOS, watchOS). Successful exploitation can lead to arbitrary code execution.
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.2= 34= 35= 10.0= 11.0< 15.2< 15.2>= 12.0.0, <= 12.1< 15.2< 8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 browser or WebKit runtime in useDetermine if you are running Safari on Apple devices or WebKit-based browsers (like WebKitGTK on Linux). On Apple devices, Safari is bundled with the OS.Affected if The system uses Safari or a WebKit-based browser to render web content.
-
Check Safari version on macOSOpen Safari, go to Safari > About Safari to view the version number, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal.Affected if The installed Safari version is earlier than 15.2.
-
Check iOS or iPadOS version on Apple mobile devicesGo to Settings > General > About to view the iOS/iPadOS version. Safari is bundled with the OS and cannot be updated separately.Affected if The iOS or iPadOS version is earlier than 15.2.
-
Check macOS version if Safari is bundledGo to Apple menu > About This Mac to view the macOS version. Safari comes pre-installed with macOS.Affected if The macOS version is 12.0.0 through 12.1 (inclusive), which ships with a vulnerable Safari version.
-
Check WebKit package version on Linux (Fedora/Debian)On Fedora, run 'dnf list installed | grep webkit'. On Debian, run 'dpkg -l | grep webkit'. For webkit2gtk-4.0 or webkit2gtk-4.1, check the specific package version.Affected if The system runs Fedora 34 or 35, or Debian 10.0 or 11.0, with a WebKit package installed.
You are affected if you are running Safari before version 15.2, iOS/iPadOS before 15.2, macOS 12.0-12.1, tvOS before 15.2, watchOS before 8.3, or a WebKit package on Fedora 34/35 or Debian 10.0/11.0, and you process untrusted web content with the vulnerable component enabled.
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.315.2
Apply the vendor patches by updating to iOS 15.2+, iPadOS 15.2+, macOS Monterey 12.1+, tvOS 15.2+, watchOS 8.3+, or Safari 15.2+. For enterprise environments, deploy updates via MDM or software distribution tools.
iOS 15.2, iPadOS 15.2, macOS Monterey 12.1, Safari 15.2, tvOS 15.2, watchOS 8.3
- For iOS devices: Upgrade to iOS 15.2 or later via Settings > General > Software Update
- For iPadOS devices: Upgrade to iPadOS 15.2 or later via Settings > General > Software Update
- For macOS Monterey: Upgrade to 12.1 or later via System Preferences > Software Update
- For Safari: Upgrade to Safari 15.2 or later (included with macOS 12.1 update)
- For tvOS devices: Upgrade to tvOS 15.2 or later via Settings > System > Software Updates
- For Apple Watch: Upgrade to watchOS 8.3 or later via the Watch app on iPhone
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30953 — 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-30953 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