FirefoxWeb browser · Mozilla
CVE-2018-5090
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 57. 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 < 58.
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 · moderate confidenceMemory safety bugs in Firefox 57 showed evidence of memory corruption that with sufficient effort could potentially be exploited to achieve arbitrary code execution.
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
<= 57.0.4
Ubuntu LinuxOperating system
= 14.04= 16.04= 17.10CVSS 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 version on desktopOpen Firefox, click menu > Help > About Firefox. The version number is displayed on this page.Affected if Version displays 57.0.4 or lower (57.0, 57.0.1, 57.0.2, 57.0.3, or 57.0.4)
-
Check Firefox version via command lineRun 'firefox --version' or 'firefox -v' in terminal. On Linux, also try 'dpkg -l | grep firefox' or 'rpm -qa | grep firefox' depending on package manager.Affected if Version output shows 57.0.4 or lower
-
Check Firefox package version on Ubuntu systemsRun 'dpkg -l | grep -i firefox' or check /usr/lib/firefox/ folder for version files. Also check snap/flatpak versions if used.Affected if Package version listed is 57.0.4 or lower
-
Verify Firefox is actually vulnerable (not already updated)Confirm the installed build date and update status via Help > About Firefox. If it shows it is up to date with version 57.x, it is still affected.Affected if Firefox reports as current/up-to-date at version 57.x or below
User is affected if Firefox is installed at version 57.0.4 or any lower 57.x version (57.0 through 57.0.3).
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 · scopedUpgrade Firefox to version 58 or later to remediate the memory corruption vulnerability.
Firefox 58.0 or later (preferably latest stable release)
- Back up any important Firefox data (bookmarks, passwords, preferences)
- Close all running Firefox instances
- For Windows/macOS: Download Firefox 58.0 or later from the official Mozilla website (www.mozilla.org)
- For Linux: Run 'sudo apt-get update && sudo apt-get upgrade firefox' to apply security updates
- After upgrade, verify the version by navigating to 'about:firefox' in the address bar
- Ensure the version shows 58.0 or higher
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5090 — 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-2018-5090 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