dbcve.org
FirefoxWeb browser · Mozilla

CVE-2017-5392

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 51.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
Weak proxy objects have weak references on multiple threads when they should only have them on one, resulting in incorrect memory usage and corruption, which leads to potentially exploitable crashes. Note: This issue only affects Firefox for Android. Other operating systems are not affected. This vulnerability affects Firefox < 51.

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

A race condition in Firefox for Android causes weak proxy objects to incorrectly maintain weak references across multiple threads instead of a single thread. This leads to memory corruption and potentially exploitable crashes. The issue is specific to Firefox for Android versions prior to 51.

MitigationUpdate Firefox for Android to version 51 or later. Organizations should leverage mobile device management (MDM) tools to identify and remediate outdated installations.

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
FirefoxWeb browser
Affected:< 51.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. Confirm Firefox for Android is installed
    Use 'adb shell pm list packages mozilla' or check installed apps on the Android device to identify the Firefox package. The vulnerable product is Firefox for Android, not desktop Firefox.
    Affected if No Firefox for Android package is found on the device
  2. Identify the Firefox package name on Android
    Run 'adb shell pm list packages | grep -i mozilla' to list Mozilla packages installed. Firefox for Android typically uses package names like 'org.mozilla.firefox' or 'org.mozilla.fennec_aurora'.
    Affected if The package name does not indicate Firefox for Android (e.g., 'org.mozilla.firefox' for release, 'org.mozilla.fennec_aurora' for nightly)
  3. Retrieve the installed Firefox for Android version
    Run 'adb shell dumpsys package <package_name>' and look for 'versionName' in the output, or check the app version in Android Settings > Apps > Firefox.
    Affected if The version cannot be determined or the device is not running Android
  4. Compare the installed version against the affected range
    Compare the version identified in the previous step to the vulnerable range: any version before 51.0 (e.g., 50.0, 49.0, 48.0).
    Affected if The installed version is a release earlier than 51.0 (for example, 50.1, 48.2, or any 50.x/49.x/48.x release)

The environment is affected if Firefox for Android is installed with any version prior to 51.0 on an Android device.

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 51.0 or later
Fixed in 51.0
Interim mitigation

Update Firefox for Android to version 51 or later. Organizations should leverage mobile device management (MDM) tools to identify and remediate outdated installations.

Recommended fix High confidence

Firefox 51.0 (or later) for Android

  1. Open the Google Play Store on your Android device
  2. Search for Firefox or Mozilla Firefox
  3. If an update is available, tap 'Update' to install Firefox 51.0 or later
  4. If the app does not show an update, uninstall the current version and reinstall Firefox from the Play Store to get the latest version (51.0+)
  5. After updating, verify the version by going to Menu > Settings > Firefox version to confirm you are on 51.0 or higher
Caveat Minimal risk; this is a security update. Some legacy add-ons or extensions may not be compatible with newer Firefox versions, but the version 51.0 release had no major breaking changes for typical users.

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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