CVE-2017-5429
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 · uneditedMemory safety bugs were reported in Firefox 52, Firefox ESR 45.8, Firefox ESR 52, and Thunderbird 52. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code. This vulnerability affects Thunderbird < 52.1, Firefox ESR < 45.9, Firefox ESR < 52.1, and Firefox < 53.
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 confidenceMemory safety bugs in Firefox and Thunderbird allowed memory corruption that could be exploited for arbitrary code execution. The vulnerability stems from multiple memory handling issues in the affected versions.
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= 6.0= 7.0= 6.0= 7.0= 6.0= 7.0= 8.0< 45.9.0< 53.0= 52.0< 52.1.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 installed Firefox versionRun: firefox --version OR look at Help > About Firefox in the application menuAffected if Version is less than 45.9.0, OR between 45.9.0 and 52.0 (inclusive), OR exactly 52.0. The fixed version is 53.0 or later.
-
Check installed Thunderbird versionRun: thunderbird --version OR look at Help > About Thunderbird in the application menuAffected if Version is less than 52.1.0. The fixed version is 52.1.0 or later.
-
Check for Firefox ESR versionRun: firefox --version and note if it is an ESR (Extended Support Release) build. ESR versions are labeled as such in the application.Affected if Firefox ESR version is less than 45.9 ESR OR less than 52.1 ESR.
-
Verify Firefox is actually in useConfirm Firefox browser is installed and executable on the system by running: which firefoxAffected if Firefox is installed and the version falls within the affected ranges listed above.
A user is affected if Firefox version is less than 53.0 (or less than 45.9 ESR / 52.1 ESR for ESR releases) OR Thunderbird version is less than 52.1.0.
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.9.052.1.053.0
Update affected installations to Firefox 53 or later, Firefox ESR 45.9/52.1 or later, or Thunderbird 52.1 or later to remediate this critical vulnerability.
Firefox >= 53 (or Firefox ESR >= 45.9 or >= 52.1 depending on ESR branch); Thunderbird >= 52.1
- Identify the currently installed Firefox or Thunderbird version using 'firefox --version' or 'thunderbird --version'
- For Fedora/RHEL/CentOS systems: Run 'sudo dnf update firefox thunderbird' or 'sudo yum update firefox thunderbird' to install the latest available security update
- For Debian/Ubuntu systems: Run 'sudo apt-get update && sudo apt-get install firefox thunderbird' to get the latest package versions
- If using Firefox ESR: Ensure upgrade to ESR 45.9+, ESR 52.1+, or latest ESR release
- If using Thunderbird: Ensure upgrade to version 52.1 or later
- If using Firefox (non-ESR): Ensure upgrade to version 53 or later
- Restart the browser/application after update completes
- Verify the installed version matches or exceeds the fixed version using 'firefox --version' or 'thunderbird --version'
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-2017-5429 — 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-5429 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