CVE-2019-11693
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 bufferdata function in WebGL is vulnerable to a buffer overflow with specific graphics drivers on Linux. This could result in malicious content freezing a tab or triggering a potentially exploitable crash. *Note: this issue only occurs on Linux. Other operating systems are unaffected.*. This vulnerability affects Thunderbird < 60.7, Firefox < 67, and Firefox ESR < 60.7.
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 confidenceA buffer overflow vulnerability exists in the WebGL bufferdata function within Firefox, Firefox ESR, and Thunderbird on Linux systems with specific graphics drivers. The overflow occurs when processing WebGL buffer data and can cause a tab to freeze or crash, with potential for exploitation. This issue is specific to Linux platforms; Windows and macOS are unaffected.
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< 60.7.0< 67.0< 60.7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the operating system is LinuxRun 'uname -s' or check system documentation. This vulnerability affects only Linux platforms; Windows and macOS are unaffected by CVE-2019-11693.Affected if The system is running Linux. If running Windows or macOS, this CVE does not apply.
-
Check Firefox versionRun 'firefox --version' in the terminal. Compare the installed version against the affected ranges: any version less than 60.7.0, or any version from 60.7.0 up to but not including 67.0.Affected if Firefox is installed with a version less than 60.7.0, or between 60.7.0 and 67.0 (excluding 67.0).
-
Check Thunderbird versionRun 'thunderbird --version' in the terminal. Compare the installed version against the affected range: any version less than 60.7.0.Affected if Thunderbird is installed with a version less than 60.7.0.
-
Verify WebGL usageIn Firefox, access about:config and search for 'webgl.enabled-for-all-sites'. Check if WebGL is in use by visiting any site that utilizes WebGL graphics. This vulnerability is triggered through the WebGL bufferdata function.Affected if WebGL is enabled and actively used in the browser. If WebGL is disabled, the vulnerable code path is not triggered.
A system is affected if it runs Linux with an unpatched Firefox version (less than 60.7.0 or between 60.7.0 and 67.0) or unpatched Thunderbird version (less than 60.7.0), and WebGL is enabled or used.
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.
dbcve · scoped60.7.067.0
Update affected applications to the patched versions: Firefox 67 or later, Firefox ESR 60.7 or later, or Thunderbird 60.7 or later. Organizations should deploy these updates through their patch management processes.
Firefox 67.0+ (or Firefox ESR 60.7+); Thunderbird 60.7.0+
- 1. Check the current Firefox or Thunderbird version by navigating to Help > About (Firefox) or Help > About Thunderbird
- 2. For Firefox: If running version < 67.0, upgrade to Firefox 67.0 or later; if running ESR version < 60.7, upgrade to Firefox ESR 60.7 or later
- 3. For Thunderbird: If running version < 60.7.0, upgrade to Thunderbird 60.7.0 or later
- 4. Download the latest version from the official Mozilla website (www.mozilla.org) or use the built-in update mechanism
- 5. Restart the application after upgrade completes
- 6. Verify the upgrade was successful by checking Help > About again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11693 — 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-2019-11693 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