dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-7810

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 52.4.0 / 56.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 55 and Firefox ESR 52.3. 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 Firefox < 56, Firefox ESR < 52.4, and Thunderbird < 52.4.

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 vulnerability in Firefox 55 and Firefox ESR 52.3 causing memory corruption, potentially allowing arbitrary code execution via specially crafted web content.

MitigationUpgrade to Firefox 56+, Firefox ESR 52.4+, or Thunderbird 52.4+ to apply the memory safety fixes.

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
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.4
Enterprise Linux Server EusOperating system
Affected:= 7.4= 7.5
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Ubuntu LinuxOperating system
Affected:= 17.10= 18.04
FirefoxWeb browser
Affected:< 56.0< 52.4.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. Identify if Firefox is installed
    Check for the presence of the Firefox binary or package. On Linux systems, run: which firefox, dpkg -l firefox, or rpm -qa firefox. On Windows, check Program Files for Mozilla Firefox folder.
    Affected if Firefox is not found on the system, this CVE does not apply.
  2. Determine the installed Firefox version
    Run 'firefox --version' or 'firefox -v' from the command line. On Linux, you can also use: dpkg -l firefox | grep firefox (Debian/Ubuntu) or rpm -qi firefox (RHEL).
    Affected if Command returns an error or no version is displayed.
  3. Compare against vulnerable version ranges
    Examine the version number obtained. For standard Firefox: vulnerable if version < 56.0. For Firefox ESR: vulnerable if version < 52.4.0.
    Affected if Version is below 56.0 for standard Firefox OR version is below 52.4.0 for Firefox ESR.
  4. Verify the underlying OS distribution (Linux only)
    If running on Linux, confirm the distribution: cat /etc/os-release or lsb_release -a. Check if it is Debian 7/8/9, RHEL 6/7, or Ubuntu 17.10/18.04.
    Affected if Running a Linux distribution not listed in affected versions does not automatically mean safe - always verify the Firefox version first.

A user is affected if Mozilla Firefox (standard) version is below 56.0 or Firefox ESR version is below 52.4.0, regardless of the underlying Linux distribution listed in affected products.

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.4.0 / 56.0 or later
Fixed in 52.4.056.0
Interim mitigation

Upgrade to Firefox 56+, Firefox ESR 52.4+, or Thunderbird 52.4+ to apply the memory safety fixes.

Recommended fix High confidence

Firefox 56.0+ or Firefox ESR 52.4+ or Thunderbird 52.4+

  1. For Debian/Ubuntu systems: Run 'sudo apt-get update && sudo apt-get upgrade' to receive the Firefox/Thunderbird security updates from your distribution's repositories
  2. For RHEL/CentOS systems: Run 'sudo yum update' or 'sudo dnf update' to apply the security patches
  3. For all systems: Ensure Firefox is updated to version 56.0 or later
  4. For all systems: Ensure Firefox ESR is updated to version 52.4 or later
  5. For all systems: Ensure Thunderbird is updated to version 52.4 or later
  6. Restart the browser/application after updating
Caveat Upgrading to Firefox 56 may remove support for some legacy extensions or plugins; Firefox ESR 52.4 is the extended support release with longer compatibility

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7810 — 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-7810 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