dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-5430

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 52.1.0 / 53.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Memory safety bugs were reported in Firefox 52, 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 < 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 confidence

Memory safety bugs in the Firefox/Thunderbird browser engine caused memory corruption. These vulnerabilities could potentially be exploited for arbitrary code execution via carefully crafted web content.

MitigationUpgrade to Firefox >= 53, Firefox ESR >= 52.1, or Thunderbird >= 52.1 to obtain the patched versions addressing these memory safety issues.

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
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
FirefoxWeb browser
Affected:< 52.1.0< 53.0
ThunderbirdApplication
Affected:< 52.1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Mozilla Firefox is installed
    Run 'rpm -qa | grep -i firefox' or 'which firefox' to find Firefox packages
    Affected if Firefox package is present on the system
  2. Determine installed Firefox version
    Run 'firefox --version' or 'rpm -q firefox' to get the exact version number
    Affected if Version is less than 52.1.0 or less than 53.0 (any version before the patched releases)
  3. Check if Mozilla Thunderbird is installed
    Run 'rpm -qa | grep -i thunderbird' or 'which thunderbird' to find Thunderbird packages
    Affected if Thunderbird package is present on the system
  4. Determine installed Thunderbird version
    Run 'thunderbird --version' or 'rpm -q thunderbird' to get the exact version number
    Affected if Version is less than 52.1.0

A system is affected if Mozilla Firefox before version 52.1.0/53.0 or Mozilla Thunderbird before version 52.1.0 is installed, or if the Firefox/Thunderbird packages from RHEL 7.0 are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 52.1.0 / 53.0 or later
Fixed in 52.1.053.0
Interim mitigation

Upgrade to Firefox >= 53, Firefox ESR >= 52.1, or Thunderbird >= 52.1 to obtain the patched versions addressing these memory safety issues.

Recommended fix High confidence

Firefox 53.0 or later (or Firefox ESR 52.1+); Thunderbird 52.1 or later

  1. Back up any important browser data (bookmarks, passwords, saved forms) from the current Firefox/Thunderbird installation
  2. For RHEL/CentOS systems: Run 'sudo yum update firefox' or 'sudo dnf update firefox' to install the patched version
  3. For RHEL/CentOS systems: Run 'sudo yum update thunderbird' or 'sudo dnf update thunderbird' if Thunderbird is installed
  4. Alternatively, download Firefox 53.0 or later from https://www.mozilla.org/firefox/
  5. Alternatively, download Thunderbird 52.1 or later from https://www.mozilla.org/thunderbird/
  6. Restart the browser/application after updating to apply the security fixes
Caveat Some older extensions or plugins may be incompatible with newer Firefox versions; test critical workflows before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5430 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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