FirefoxWeb browser · Mozilla

CVE-2020-12423

HIGH · 7.8 CVSS v3.1 Published 2020-07-09
Fix available
A fix is available. Upgrade to 78.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
When the Windows DLL "webauthn.dll" was missing from the Operating System, and a malicious one was placed in a folder in the user's %PATH%, Firefox may have loaded the DLL, leading to arbitrary code execution. *Note: This issue only affects the Windows operating system; other operating systems are unaffected.* This vulnerability affects Firefox < 78.

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 DLL hijacking vulnerability in Firefox on Windows where the application loads a malicious webauthn.dll from a user-controlled PATH directory when the legitimate system DLL is missing, allowing arbitrary code execution.

MitigationUpdate Firefox to version 78 or later. Additionally, audit the user PATH environment variable for untrusted directories and ensure the legitimate webauthn.dll is present in the Windows System32 directory.

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:< 78.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check installed Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line, or check Add/Remove Programs for Mozilla Firefox
    Affected if Version is below 78.0 (any version starting with 77.x or earlier)
  2. Verify webauthn.dll presence in System32
    Open File Explorer and navigate to C:\Windows\System32\webauthn.dll, or run 'dir C:\Windows\System32\webauthn.dll' in command prompt
    Affected if The file does NOT exist (is missing from the legitimate system directory)
  3. Audit PATH environment variable for untrusted directories
    Open System Properties > Environment Variables, or run 'echo %PATH%' in command prompt, and review all directories listed
    Affected if PATH contains user-writable directories outside of system folders (such as temp folders, downloads, or untrusted third-party locations)
  4. Confirm Firefox is running on Windows
    Verify the operating system is Windows (the vulnerability only affects Firefox on Windows)
    Affected if Running Windows OS with Firefox installed

You are affected if Firefox version is below 78.0 AND webauthn.dll is missing from System32 AND your PATH contains user-controllable directories, allowing Firefox to load a malicious DLL from that PATH.

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.

From vendor data
Upgrade available Upgrade to 78.0 or later
Fixed in 78.0
Interim mitigation

Update Firefox to version 78 or later. Additionally, audit the user PATH environment variable for untrusted directories and ensure the legitimate webauthn.dll is present in the Windows System32 directory.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-12423 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