FirefoxWeb browser · Mozilla
CVE-2019-11713
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 · uneditedA use-after-free vulnerability can occur in HTTP/2 when a cached HTTP/2 stream is closed while still in use, resulting in a potentially exploitable crash. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.
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 use-after-free vulnerability exists in the HTTP/2 implementation where a cached HTTP/2 stream is closed while still in active use, causing the memory to be freed but still being referenced. This leads to a potentially exploitable crash that could allow arbitrary code execution.
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
< 60.8.0< 68.0< 60.8.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.
-
Check Firefox versionIn Firefox, go to Help > About Firefox (or navigate to about:support) to view the installed version numberAffected if The version is below 60.8.0 or below 68.0 (any version before 68.0 is affected)
-
Check Thunderbird versionIn Thunderbird, go to Help > About Thunderbird to view the installed version numberAffected if The version is below 60.8.0
-
Confirm HTTP/2 is in useThis vulnerability requires active HTTP/2 connections. In Firefox, navigate to about:networking and check the HTTP/2 session status, or use browser developer tools (Network tab) to inspect connection protocol headersAffected if HTTP/2 sessions are active while running an affected version; the vulnerability triggers when an HTTP/2 stream is closed while still in active use
You are affected if you run Firefox before version 68.0 (or before 60.8.0 on ESR branches) or Thunderbird before version 60.8.0, and you use HTTP/2 connections which are enabled by default in these products.
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.8.068.0
Upgrade to Firefox ESR 60.8 or later, Firefox 68 or later, or Thunderbird 60.8 or later to resolve the vulnerability.
Firefox ESR >= 60.8, Firefox >= 68.0, Thunderbird >= 60.8
- Identify the installed Firefox or Thunderbird version (Help > About or check via command line)
- For Firefox: If running ESR, upgrade to version 60.8 or later; if running regular Firefox, upgrade to version 68.0 or later
- For Thunderbird: Upgrade to version 60.8 or later
- Download the appropriate fixed version from the official Mozilla website (https://www.mozilla.org/) or use your system's package manager to update
- Close all running instances of the browser or email client
- Install the updated version and restart the application
- Verify the installed version matches or exceeds the minimum fixed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11713 — 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-11713 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