CVE-2017-5464
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 · uneditedDuring DOM manipulations of the accessibility tree through script, the DOM tree can become out of sync with the accessibility tree, leading to memory corruption and a potentially exploitable crash. 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 confidenceA race condition exists in Firefox and Thunderbird where DOM manipulations through script can cause the accessibility tree to become desynchronized from the actual DOM tree. This state leads to memory corruption and potentially exploitable crashes due to the mismatch between what the accessibility layer expects and the actual DOM structure.
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= 8.0= 6.0= 7.0= 6.0= 7.0= 6.0= 7.0= 7.3= 7.4= 7.3= 7.4= 7.5= 6.0= 7.0< 53.0= 52.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.
-
Identify installed Mozilla productRun 'rpm -qa | grep -i firefox' or 'rpm -qa | grep -i thunderbird' on RHEL-based systems, or 'dpkg -l | grep -i firefox' or 'dpkg -l | grep -i thunderbird' on Debian-based systems to see which Mozilla product is installedAffected if Firefox or Thunderbird is installed
-
Determine Firefox versionRun 'firefox --version' or check 'Help > About Firefox' in the GUI to obtain the exact version numberAffected if Firefox version is less than 53.0 or specifically 52.0.x
-
Determine Thunderbird versionRun 'thunderbird --version' or check 'Help > About Thunderbird' in the GUI to obtain the exact version numberAffected if Thunderbird is installed and version is affected per vendor advisories (less than 52.1)
-
Check if accessibility features are enabledIn Firefox, go to Options > Privacy & Security > Accessibility and verify if 'Always use the accessibility service' is enabled; on Linux systems, check if assistive technologies are loaded by examining /etc/passwd for users with assistive technology flags or running 'gsettings get org.gnome.desktop.interface toolkit-accessibility'Affected if Accessibility features are enabled (this is required for the vulnerability to be exploitable as the flaw involves desynchronization of the accessibility tree)
You are affected if you have Firefox version < 53.0 (or specifically 52.0.x) or an affected Thunderbird version, AND the accessibility feature is enabled in your browser configuration.
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 · scoped53.0
Apply the vendor-supplied patches by upgrading to Firefox 53+, Firefox ESR 52.1+, Firefox ESR 45.9+, or Thunderbird 52.1+ as appropriate for the affected installation.
Firefox 53.0+, Firefox ESR 45.9+, Firefox ESR 52.1+, Thunderbird 52.1+ (or vendor-provided patched packages for Linux distributions)
- 1. Identify the installed Firefox/Thunderbird version by navigating to Help > About (or checking the package manager)
- 2. For Firefox: Upgrade to version 53.0 or later (recommended: latest stable release)
- 3. For Firefox ESR: If on ESR 45.x, upgrade to 45.9 or later; if on ESR 52.x, upgrade to 52.1 or later
- 4. For Thunderbird: Upgrade to version 52.1 or later
- 5. For Linux distributions (Debian 8.0, RHEL 6/7): Apply vendor security updates via package manager (apt-get update && apt-get upgrade for Debian; yum update for RHEL)
- 6. Restart the application after upgrading
- 7. Verify the installed version matches or exceeds the fixed version numbers above
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5464 — 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-5464 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