dbcve.org
FirefoxWeb browser · Mozilla

CVE-2018-12407

CRITICAL · 9.8 CVSS v3.0 Published 2019-02-28
Fix available
A fix is available. Upgrade to 64.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
A buffer overflow occurs when drawing and validating elements with the ANGLE graphics library, used for WebGL content, when working with the VertexBuffer11 module. This results in a potentially exploitable crash. This vulnerability affects Firefox < 64.

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

A buffer overflow vulnerability exists in the ANGLE graphics library's VertexBuffer11 module used for WebGL content rendering in Firefox. The overflow occurs during element drawing and validation operations, potentially allowing an attacker to execute arbitrary code or cause a denial of service via a specially crafted WebGL payload.

MitigationUpdate Firefox to version 64 or later. For applications embedding ANGLE directly, update the ANGLE library to a version containing bounds checking fixes in the VertexBuffer11 module.

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:< 64.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 18.04= 18.10

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Check installed Firefox version
    Run 'firefox --version' from command line, or open Firefox and go to Help > About Firefox
    Affected if Version displayed is earlier than 64.0 (e.g., 63.x, 62.x, etc.)
  2. Check if WebGL is enabled in Firefox
    Open 'about:support' in Firefox address bar and look for 'WebGL Renderer' entry under Graphics, or check the 'webgl.disabled' boolean in 'about:config'
    Affected if WebGL is enabled (webgl.disabled is not set to true) - the vulnerability only triggers during WebGL rendering operations
  3. Check Ubuntu Firefox package version (Ubuntu systems only)
    Run 'dpkg -l | grep firefox' or 'apt list --installed | grep firefox' to see the installed Firefox package version
    Affected if Package version is earlier than 64.0+build1-0ubuntu0.14.04.1 (or corresponding version for 16.04/18.04/18.10)

You are affected if running Firefox version earlier than 64.0 with WebGL enabled in your browser, as the buffer overflow in the ANGLE VertexBuffer11 module triggers during WebGL content rendering.

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 64.0 or later
Fixed in 64.0
Interim mitigation

Update Firefox to version 64 or later. For applications embedding ANGLE directly, update the ANGLE library to a version containing bounds checking fixes in the VertexBuffer11 module.

Recommended fix High confidence

Firefox 64.0 or later (or Ubuntu patched firefox package from USN for 14.04/16.04/18.04/18.10)

  1. Backup important browser data (bookmarks, passwords, etc.) as a precautionary measure
  2. Update your package repository lists: sudo apt-get update
  3. Upgrade Firefox to version 64.0 or later: sudo apt-get upgrade firefox (Ubuntu) or download from mozilla.org
  4. Alternatively, apply Ubuntu security patches: sudo apt-get update && sudo apt-get install firefox (for Ubuntu 14.04, 16.04, 18.04, 18.10)
  5. Restart Firefox after upgrade
  6. Verify Firefox version by navigating to about:firefox - confirm version is 64.0 or higher
Caveat Minor: Some legacy extensions may be incompatible with Firefox 64; review add-ons after upgrade

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-12407 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