CVE-2017-5400
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 · uneditedJIT-spray targeting asm.js combined with a heap spray allows for a bypass of ASLR and DEP protections leading to potential memory corruption attacks. This vulnerability affects Firefox < 52, Firefox ESR < 45.8, Thunderbird < 52, and Thunderbird < 45.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 confidenceJIT-spray attacks targeting asm.js combined with heap spray techniques bypass ASLR and DEP memory protections, enabling memory corruption and potential arbitrary code execution in affected Mozilla products.
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= 5.0= 6.0= 7.0= 5.0= 6.0= 7.0= 7.3= 7.4= 7.3= 7.4= 7.5= 5.0= 6.0= 7.0= 8.0< 45.8.0< 52.0< 45.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 if Firefox is installedRun 'firefox --version' or check for Firefox in /usr/bin/firefox or look for the firefox package using your system package manager (rpm -q firefox or dpkg -l firefox)Affected if Firefox is installed and its version is below 52.0 (with critical risk at versions below 45.8.0)
-
Check if Thunderbird is installedRun 'thunderbird --version' or check for Thunderbird in /usr/bin/thunderbird or look for the thunderbird package using your system package manager (rpm -q thunderbird or dpkg -l thunderbird)Affected if Thunderbird is installed and its version is below 45.8.0
-
Determine exact Firefox versionRun 'firefox --version' to get the precise version number, or check the package details with 'rpm -qi firefox' or 'dpkg -s firefox'Affected if Version shown is less than 45.8.0 (definitely affected) or between 45.8.0 and 52.0 (affected per vendor scope)
-
Determine exact Thunderbird versionRun 'thunderbird --version' to get the precise version number, or check the package details with 'rpm -qi thunderbird' or 'dpkg -s thunderbird'Affected if Version shown is less than 45.8.0
You are affected if Firefox version is below 52.0 (especially below 45.8.0) or Thunderbird version is below 45.8.0, as the JIT-spray vulnerability exists in these unpatched Mozilla product versions.
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 · scoped45.8.052.0
Upgrade to Firefox 52+, Firefox ESR 45.8+, Thunderbird 52+, or Thunderbird ESR 45.8+ to patch this vulnerability.
Firefox 52.0 (or Firefox ESR 45.8); Thunderbird 52.0 (or Thunderbird ESR 45.8)
- For Firefox users: Upgrade to Firefox 52.0 or later (or Firefox ESR 45.8 or later for extended support)
- For Thunderbird users: Upgrade to Thunderbird 52.0 or later (or Thunderbird ESR 45.8 or later)
- On RHEL/CentOS systems: Run 'yum update firefox' or 'yum update thunderbird' to apply vendor security updates
- On Debian/Ubuntu systems: Run 'apt-get update && apt-get install firefox' or 'apt-get update && apt-get install thunderbird'
- Restart the browser/application after updating to ensure the patched version is loaded
- Verify the installed version by checking Help > About Firefox or About Thunderbird
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5400 — 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-2017-5400 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