CVE-2018-12377
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 when refresh driver timers are refreshed in some circumstances during shutdown when the timer is deleted while still in use. This results in a potentially exploitable crash. This vulnerability affects Firefox < 62, Firefox ESR < 60.2, and Thunderbird < 60.2.1.
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 the refresh driver timer mechanism where timers are deleted while still in use during application shutdown, causing a crash that could potentially be exploited for 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= 6.0= 7.0= 6.0= 7.0= 7.6= 7.5= 7.6= 7.6= 6.0= 7.0= 8.0= 9.0= 14.04= 16.04= 18.04CVSS 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.
-
Identify installed Mozilla productsRun 'rpm -qa | grep -i firefox' for RHEL/CentOS, 'dpkg -l | grep -i firefox' for Debian/Ubuntu, or check Thunderbird with 'rpm -qa | grep -i thunderbird' / 'dpkg -l | grep -i thunderbird'Affected if Firefox or Thunderbird is installed on the system
-
Get Firefox versionRun 'firefox --version' or check the package version via 'rpm -q firefox' / 'dpkg -s firefox'Affected if Version is earlier than 62.0 for standard Firefox, or earlier than 60.2 for Firefox ESR
-
Get Thunderbird versionRun 'thunderbird --version' or check the package version via 'rpm -q thunderbird' / 'dpkg -s thunderbird'Affected if Version is earlier than 60.2.1 for Thunderbird
The system is affected if Firefox versions below 62.0 (or ESR below 60.2) or Thunderbird versions below 60.2.1 are installed and the application uses the refresh driver timer functionality.
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 to Firefox 62+, Firefox ESR 60.2+, or Thunderbird 60.2.1+ to patch the timer management flaw in the refresh driver.
Firefox 62+, Firefox ESR 60.2+, or Thunderbird 60.2.1+
- Identify which application is affected: Firefox, Firefox ESR, or Thunderbird
- For Red Hat Enterprise Linux systems, update the affected package using: yum update firefox OR yum update thunderbird
- For Debian systems, update using: apt-get update && apt-get install firefox or apt-get install thunderbird
- For Ubuntu systems, update using: apt-get update && apt-get install firefox or apt-get install thunderbird
- After updating, verify the installed version matches or exceeds: Firefox 62, Firefox ESR 60.2, or Thunderbird 60.2.1
- Restart the application to ensure the fixed version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12377 — 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 sources- bugzilla.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.securityfocus.com
- www.securitytracker.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- lists.debian.org
- security.gentoo.org
- security.gentoo.org
- usn.ubuntu.com
- usn.ubuntu.com
- www.debian.org
- www.debian.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-12377 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