FirefoxWeb browser · Mozilla
CVE-2019-11707
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 type confusion vulnerability can occur when manipulating JavaScript objects due to issues in Array.pop. This can allow for an exploitable crash. We are aware of targeted attacks in the wild abusing this flaw. This vulnerability affects Firefox ESR < 60.7.1, Firefox < 67.0.3, and Thunderbird < 60.7.2.
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 type confusion vulnerability exists in the Array.pop JavaScript method in Mozilla products. The flaw allows manipulation of JavaScript objects in an unexpected way, leading to memory corruption that can be exploited for arbitrary code execution or crashes. This is a critical memory safety issue in the SpiderMonkey JavaScript engine.
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.7.1< 67.0.3< 60.7.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify installed Mozilla productOpen the application and navigate to Help > About (Firefox or Thunderbird) to display the version window, or run 'firefox --version' or 'thunderbird --version' from command lineAffected if The product is Firefox or Thunderbird
-
Check Firefox version against affected rangesCompare the installed Firefox version to: < 60.7.1 (for ESR versions below 60.7) or < 67.0.3 (for standard releases below 67.0.3)Affected if Installed version is less than 60.7.1 for ESR or less than 67.0.3 for standard release
-
Check Thunderbird version against affected rangesCompare the installed Thunderbird version to: < 60.7.2Affected if Installed version is less than 60.7.2
A user is affected if they are running Firefox (any version below 60.7.1 for ESR or below 67.0.3 for standard release) or Thunderbird below 60.7.2.
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.160.7.267.0.3
Apply vendor-supplied patches by updating Firefox to version 67.0.3 or later, Firefox ESR to 60.7.1 or later, and Thunderbird to 60.7.2 or later. Monitor for indicators of compromise given confirmed active exploitation in the wild.
Firefox 67.0.3, Firefox ESR 60.7.1, or Thunderbird 60.7.2
- Back up your Firefox/Thunderbird profile data to prevent data loss
- Download the appropriate fixed version: Firefox 67.0.3, Firefox ESR 60.7.1, or Thunderbird 60.7.2 from the official Mozilla website
- Close all instances of Firefox or Thunderbird
- Install the downloaded update
- Restart the application and verify functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Exploited in the wild — priority engagement
- 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-2019-11707 — 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-11707 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