CVE-2018-5091
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 · uneditedA use-after-free vulnerability can occur during WebRTC connections when interacting with the DTMF timers. This results in a potentially exploitable crash. This vulnerability affects Firefox ESR < 52.6 and 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 · high confidenceA use-after-free vulnerability exists in Firefox's WebRTC implementation when handling DTMF (Dual-Tone Multi-Frequency) timers. The vulnerability allows memory to be accessed after being freed, potentially leading to arbitrary code execution or a crash.
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= 7.0= 8.0= 9.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< 58.0< 52.6.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.
-
Check if Firefox is installedRun 'which firefox' or 'rpm -q firefox' on RHEL systems, or 'dpkg -l firefox' on Debian systemsAffected if Firefox is not installed - not affected
-
Determine installed Firefox versionRun 'firefox --version' or check the package version via 'rpm -q firefox' / 'dpkg -l firefox'Affected if Version is less than 58.0, or version is between 52.0 and 52.5.x (ESR versions below 52.6)
-
Check for Firefox ESR versionRun 'firefox --version' and look for 'ESR' in the output, or check package detailsAffected if ESR version is less than 52.6.0 (for example, 52.5.x or earlier)
-
Verify WebRTC support is presentCheck if WebRTC is available in the Firefox installation by typing 'about:support' in the address bar and looking for WebRTC components, or check for webrtc* packagesAffected if WebRTC support is present in the Firefox installation
-
Check OS version for packaged FirefoxRun 'cat /etc/os-release' on Debian or 'cat /etc/redhat-release' on RHEL to identify the OS versionAffected if Running Debian 7.0, 8.0, or 9.0; or RHEL 6.x or 7.x variants with an unpatched Firefox version
You are affected if Firefox (or Firefox ESR) version is below 58.0 (or below 52.6.0 for ESR) and WebRTC functionality is present in the installation on a vulnerable OS version.
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 · scoped52.6.058.0
Update Firefox to version 58 or later, or Firefox ESR to version 52.6 or later, to patch the use-after-free in the WebRTC DTMF timer handling.
Firefox 58.0 or later (standard), Firefox ESR 52.6.0 or later
- Identify the installed Firefox version by navigating to Menu > Help > About Firefox (or typing 'about:support' in the address bar)
- For Debian systems: Run 'apt-get update && apt-get upgrade' to receive the fixed Firefox package from Debian security repositories
- For RHEL/CentOS systems: Run 'yum update firefox' to receive the fixed Firefox package from Red Hat repositories
- Alternatively, download Firefox 58.0 or later directly from the official Mozilla website (getfirefox.com)
- Alternatively, download Firefox ESR 52.6 or later from Mozilla for enterprise deployments
- Restart Firefox after upgrading to ensure the new version is loaded
- Verify the fix by checking the Firefox version (should be >= 58.0 or >= 52.6.0 for ESR)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5091 — 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-5091 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