FirefoxWeb browser · Mozilla
CVE-2014-1502
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 · uneditedThe (1) WebGL.compressedTexImage2D and (2) WebGL.compressedTexSubImage2D functions in Mozilla Firefox before 28.0 and SeaMonkey before 2.25 allow remote attackers to bypass the Same Origin Policy and render content in a different domain via unspecified vectors.
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 confidenceThe WebGL.compressedTexImage2D and WebGL.compressedTexSubImage2D functions in Firefox before 28.0 and SeaMonkey before 2.25 contain a Same Origin Policy bypass vulnerability. This allows a malicious page to potentially render or access content from a different domain via unspecified vectors in these WebGL texture functions.
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
FirefoxWeb browser
< 28.0= 13.1= 11.4= 12.3= 11= 11= 11= 11.3< 2.25CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 installed Mozilla productCheck if Firefox or SeaMonkey is installed. In Firefox, enter 'about:support' in the address bar. In SeaMonkey, go to Help > About SeaMonkey. Look for the application name in the page that loads.Affected if The product is Firefox or SeaMonkey
-
Check Firefox versionIn Firefox, type 'about:support' in the address bar and look for the version number under 'Application Basics'. Compare the version to 28.0.Affected if Firefox version is less than 28.0
-
Check SeaMonkey versionIn SeaMonkey, go to Help > About SeaMonkey and note the version number displayed. Compare to 2.25.Affected if SeaMonkey version is less than 2.25
-
Verify WebGL is enabledIn Firefox, type 'about:support' and search for 'WebGL' in the page. In SeaMonkey, check if WebGL is enabled in Edit > Preferences > Advanced > Graphics. The vulnerability requires WebGL to be enabled for exploitation.Affected if WebGL is enabled in the browser settings
A user is affected if they run Firefox below version 28.0 or SeaMonkey below version 2.25 with WebGL 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.
From vendor data2.2528.0
Upgrade to Firefox 28.0 or later, or SeaMonkey 2.25 or later to patch this Same Origin Policy bypass vulnerability in the WebGL texture functions.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1502 — 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-2014-1502 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