FirefoxWeb browser · Mozilla

CVE-2014-1556

HIGH · 9.3 CVSS v2.0 Published 2014-07-23
Fix available
A fix is available. Upgrade to after 30.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Mozilla Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7 allow remote attackers to execute arbitrary code via crafted WebGL content constructed with the Cesium JavaScript library.

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 confidence

Mozilla Firefox and Thunderbird contain a use-after-free vulnerability in their WebGL implementation when processing specially crafted WebGL content using the Cesium JavaScript library. This allows remote attackers to execute arbitrary code via malicious WebGL content.

MitigationUpdate Firefox to version 31.0 or later, Firefox ESR to 24.7 or later, or Thunderbird to 24.7 or later. Alternatively, disable WebGL in browser settings as a temporary workaround.

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
Affected:<= 30.0= 24.0= 24.0.1= 24.0.2= 24.1.0= 24.1.1
Firefox EsrWeb browser
Affected:= 24.2= 24.3= 24.4= 24.5= 24.6
ThunderbirdApplication
Affected:<= 24.6= 24.0= 24.0.1= 24.1= 24.1.1= 24.2= 24.3= 24.4= 24.5

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Firefox version
    Open Firefox, click the menu button, select Help, then About Firefox. The version number is displayed on the page.
    Affected if The version is 30.0 or lower, or matches 24.0, 24.0.1, 24.0.2, 24.1.0, or 24.1.1.
  2. Identify installed Firefox ESR version
    For Firefox ESR, open the menu, go to Help, then About Firefox. ESR versions are labeled as 'Firefox ESR' on the about page.
    Affected if The version is 24.2, 24.3, 24.4, 24.5, or 24.6.
  3. Identify installed Thunderbird version
    Open Thunderbird, click the menu, select Help, then About Thunderbird.
    Affected if The version is 24.6 or lower, or matches 24.0, 24.0.1, 24.1, 24.1.1, 24.2, 24.3, 24.4, or 24.5.
  4. Verify if WebGL is enabled
    In the browser address bar, type 'about:config', press Enter, then search for 'webgl.disabled'. Check the value column.
    Affected if webgl.disabled is set to false, meaning WebGL is enabled.
  5. Check for Cesium JavaScript library usage
    Inspect web content or local files for inclusion of the Cesium library (typically via script tag referencing 'cesium.js' or 'Cesium.js').
    Affected if WebGL content using the Cesium library is loaded or visited.

A user is affected if they run Firefox or Thunderbird at any of the listed affected versions AND have WebGL enabled AND encounter WebGL content using the Cesium library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 30.0
Interim mitigation

Update Firefox to version 31.0 or later, Firefox ESR to 24.7 or later, or Thunderbird to 24.7 or later. Alternatively, disable WebGL in browser settings as a temporary workaround.

Recommended fix High confidence

Firefox 31.0+ / Firefox ESR 24.7+ / Thunderbird 24.7+

  1. Upgrade Firefox to version 31.0 or later
  2. If using Firefox ESR, upgrade to version 24.7 or later
  3. If using Thunderbird, upgrade to version 24.7 or later
  4. After upgrading, verify WebGL functionality works correctly
Caveat Minimal expected breaking changes; upgrade addresses critical code execution vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1556 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1556 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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