dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-25740

HIGH · 8.8 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 110.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
After downloading a Windows <code>.scf</code> script from the local filesystem, an attacker could supply a remote path that would lead to unexpected network requests from the operating system. This also had the potential to leak NTLM credentials to the resource.<br>*This bug only affects Firefox for Windows. Other operating systems are unaffected.*. This vulnerability affects Firefox < 110.

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

Firefox for Windows fails to properly sandbox .scf file handling after download, allowing an attacker to supply a remote path that triggers unexpected network requests from the OS. This can lead to NTLM credential leakage to a remote resource.

MitigationUpgrade Firefox to version 110 or later on all Windows systems. Until upgraded, avoid downloading .scf files from untrusted sources or disable NTLM authentication to external resources.

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:< 110.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 if Firefox is installed on Windows
    Look for firefox.exe in C:\Program Files\Mozilla Firefox\ or C:\Program Files (x86)\Mozilla Firefox\, or query the registry key HKLM\SOFTWARE\Mozilla\Mozilla Firefox
    Affected if Firefox is found on the Windows system
  2. Determine the installed Firefox version
    Run 'firefox --version' in command prompt, or right-click firefox.exe and select Properties > Details > File Version, or read the 'CurrentVersion' value from the registry key HKLM\SOFTWARE\Mozilla\Mozilla Firefox
    Affected if Unable to retrieve the version number or version is below 110.0
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions less than 110.0 (including 109.x, 108.x, and earlier) are vulnerable
    Affected if Installed version is 109.x or earlier
  4. Confirm the OS is Windows
    Verify the operating system is Windows - the .scf file sandbox bypass and NTLM leakage only apply to Windows environments
    Affected if The system is running Windows and Firefox version is below 110.0

A Windows system with Firefox version lower than 110.0 is affected by this vulnerability.

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

Upgrade Firefox to version 110 or later on all Windows systems. Until upgraded, avoid downloading .scf files from untrusted sources or disable NTLM authentication to external resources.

Recommended fix High confidence

Firefox 110.0 or later

  1. 1. Open Firefox browser
  2. 2. Navigate to Help > About Firefox (or click the menu button > Help > About Firefox)
  3. 3. The browser will automatically check for and download the latest version
  4. 4. If Firefox 110.0 or later is available, click 'Restart to Update Firefox'
  5. 5. Verify the update by returning to About Firefox and confirming the version number is 110.0 or higher
  6. 6. Alternatively, download Firefox 110.0 or later directly from the official Mozilla website at www.mozilla.org
Caveat Major browser updates may cause incompatibility with older browser extensions or add-ons; test critical workflows after upgrading

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

Fix this in Firefox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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