dbcve.org
FirefoxWeb browser · Mozilla

CVE-2018-5180

HIGH · 7.5 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 60.0 or later.
See remediation →
84/100
Remediation priority · High
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 use-after-free vulnerability can occur during WebGL operations. While this results in a potentially exploitable crash, the vulnerability is limited because the memory is freed and reused in a brief window of time during the freeing of the same callstack. This vulnerability affects Firefox < 60.

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 use-after-free vulnerability exists in Firefox's WebGL implementation where memory is freed and then reused during the same callstack execution, creating a narrow exploitation window. While limited because the freed memory is quickly reallocated, this still presents a potentially exploitable crash condition.

MitigationUpgrade Firefox to version 60 or later to obtain the patch for this use-after-free vulnerability in WebGL operations.

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

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if Firefox is installed
    Run 'which firefox' or look for Firefox in /usr/bin/firefox or ~/.mozilla/
    Affected if Firefox is not installed on the system
  2. Determine installed Firefox version
    Run 'firefox --version' or 'firefox -v' in the terminal
    Affected if Version returned is less than 60.0 (e.g., 59.x, 58.x, etc.)
  3. Confirm WebGL is accessible in the browser
    In Firefox, navigate to about:support and check if 'WebGL' appears under Graphics with a renderer listed
    Affected if WebGL is enabled and functional in the browser (the vulnerability triggers when WebGL is used)

If Firefox is installed and its version is below 60.0, the environment is vulnerable to this use-after-free issue when WebGL features are accessed.

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.

From vendor data
Upgrade available Upgrade to 60.0 or later
Fixed in 60.0
Interim mitigation

Upgrade Firefox to version 60 or later to obtain the patch for this use-after-free vulnerability in WebGL operations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5180 — 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-5180 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