Ubuntu LinuxOperating system · Canonical
CVE-2015-0830
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 WebGL implementation in Mozilla Firefox before 36.0 does not properly allocate memory for copying an unspecified string to a shader's compilation log, which allows remote attackers to cause a denial of service (application crash) via crafted WebGL content.
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 implementation in Mozilla Firefox before version 36.0 has a memory allocation flaw when copying strings to a shader's compilation log. When processing malicious WebGL content with specially crafted shader code, the improper memory allocation leads to a crash (denial of service).
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
Ubuntu LinuxOperating system
= 12.04= 14.04= 14.10
FirefoxWeb browser
<= 35.0.1= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9= 13.1= 13.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 Firefox versionIn Firefox, navigate to Help > About Firefox, or enter 'about:support' in the address bar. The version number is displayed at the top. On Linux, you can also run 'firefox --version' from terminal.Affected if The version is 35.0.1 or earlier, or matches one of these legacy versions: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, or 0.9
-
Confirm WebGL is accessibleIn Firefox, navigate to 'about:support' and search for 'WebGL' in the page. Look for a 'WebGL Renderer' entry. Alternatively, visit a WebGL test site such as webglreport.com.Affected if WebGL is enabled and returns a renderer string, indicating the feature is active in the browser.
-
Check system package version on UbuntuIf Firefox was installed via apt package manager, run 'dpkg -l | grep firefox' or 'apt-cache policy firefox' in terminal.Affected if The installed firefox package version corresponds to one of the affected Ubuntu versions (12.04, 14.04, or 14.10) with Firefox <= 35.0.1
-
Check system package version on openSUSEIf Firefox was installed via zypper, run 'zypper se firefox' or 'rpm -q firefox' in terminal.Affected if The installed firefox package version corresponds to openSUSE 13.1 or 13.2 with Firefox <= 35.0.1
You are affected if you are running Firefox version 35.0.1 or earlier (including legacy versions 0.1-0.9) on Ubuntu 12.04, 14.04, 14.10, or openSUSE 13.1/13.2, and WebGL is enabled in the browser.
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 dataUpgrade Mozilla Firefox to version 36.0 or later to obtain the patched WebGL implementation.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0830 — 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-2015-0830 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