dbcve.org
FedoraOperating system · Fedoraproject

CVE-2015-7212

HIGH · 7.5 CVSS v2.0 Published 2015-12-16
Fix available
A fix is available. Upgrade to after 42.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
Integer overflow in the mozilla::layers::BufferTextureClient::AllocateForSurface function in Mozilla Firefox before 43.0 and Firefox ESR 38.x before 38.5 allows remote attackers to execute arbitrary code by triggering a graphics operation that requires a large texture allocation.

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

Integer overflow in Mozilla Firefox's graphics texture allocation (BufferTextureClient::AllocateForSurface) allows attackers to trigger allocation of undersized buffers by providing large texture dimensions, leading to heap corruption and potential arbitrary code execution.

MitigationUpgrade Firefox to version 43.0 or later (or ESR 38.5 or later). If immediate patching is not possible, consider restricting access to untrusted content that can trigger WebGL or canvas 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
FedoraOperating system
Affected:= 22= 23
FirefoxWeb browser
Affected:<= 42.0= 38.0= 38.0.1= 38.0.5= 38.1.0= 38.1.1= 38.2.0= 38.2.1= 38.3.0= 38.4.0
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.1= 13.2

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

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

  1. Check if Firefox is installed
    On Linux: rpm -q firefox or dpkg -l firefox. On Windows: Check Program Files for Mozilla Firefox folder or check registry. On macOS: Check /Applications for Firefox.app
    Affected if Firefox is not installed on the system
  2. Determine installed Firefox version
    Run firefox --version or check About Firefox from the application menu. On Windows: look at firefox.exe properties or registry. On macOS: right-click Firefox.app > Get Info
    Affected if Version is 42.0 or lower, or matches 38.0, 38.0.1, 38.0.5, 38.1.0, 38.1.1, 38.2.0, 38.2.1, 38.3.0, or 38.4.0
  3. Check if WebGL is enabled
    In Firefox address bar, type about:config and search for webgl.disabled. Alternatively, visit a WebGL test site or check through browser settings under Performance/Graphics
    Affected if WebGL is enabled (webgl.disabled is false or not set)
  4. Check if Canvas API is accessible
    Visit any website using canvas (like webgl samples) or check in about:config for canvas-related permissions. The feature is enabled by default in unpatched versions
    Affected if Canvas and WebGL features work normally without being blocked

You are affected if Firefox version is 42.0 or lower, or any of the specific 38.x versions listed, AND WebGL or Canvas features are enabled (which is the default state).

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 a release after 42.0
Interim mitigation

Upgrade Firefox to version 43.0 or later (or ESR 38.5 or later). If immediate patching is not possible, consider restricting access to untrusted content that can trigger WebGL or canvas operations.

Fix this in Fedora Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing20.0 h
  • Review / QA8.0 h
52.0 hours of engineering $8,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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