CVE-2021-1765
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 iframe sandbox enforcement. This issue is fixed in macOS Big Sur 11.2, Security Update 2021-001 Catalina, Security Update 2021-001 Mojave. Maliciously crafted web content may violate iframe sandboxing policy.
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 vulnerability in macOS where maliciously crafted web content can bypass iframe sandboxing policies. The iframe sandbox attribute is meant to restrict various browser behaviors (scripts, forms, popups, navigation) for embedded content, but this vulnerability allows those restrictions to be violated.
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= 32= 33>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7>= 11.0, < 11.2< 2.30.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Check macOS versionRun 'sw_vers' or go to Apple menu > About This Mac to view the macOS version numberAffected if The version is 10.14.x before 10.14.6, 10.15.x before 10.15.7, or 11.0-11.1 (before 11.2)
-
Check WebKitGTK version on Fedora LinuxRun 'rpm -q webkit2gtk' or 'dpkg -l webkit2gtk' depending on the package manager to query the installed WebKitGTK versionAffected if The installed version is earlier than 2.30.6 on Fedora 32 or 33
-
Identify if browsers using vulnerable WebKit are in useOn Linux systems, check which browser engines are active (webkit2gtk is common in Epiphany/Gnome Web, Midori, and other GTK-based browsers). Run 'rpm -qa | grep -i webkit' or 'dpkg -l | grep -i webkit'Affected if Any application using WebKitGTK version < 2.30.6 is in use on Fedora 32 or 33
-
Check for iframe sandbox usage in web contentSearch codebase or web content for 'sandbox=' attribute in iframe tags using grep: grep -r 'sandbox=' /path/to/webroot or inspect HTML for iframe elements with sandbox attributeAffected if The environment serves or hosts web pages containing iframe elements with sandbox attributes, as the vulnerability allows bypassing these restrictions
A system is affected if it runs macOS versions 10.14.x before 10.14.6, 10.15.x before 10.15.7, or 11.0-11.1, OR uses WebKitGTK < 2.30.6 on Fedora 32/33, AND serves or renders web content with iframe sandbox attributes.
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 data2.30.610.14.610.15.7
Apply the relevant macOS security update: macOS Big Sur 11.2, Security Update 2021-001 Catalina, or Security Update 2021-001 Mojave depending on the macOS version in use.
- 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-1765 — 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-1765 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