CVE-2023-25738
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 · uneditedMembers of the <code>DEVMODEW</code> struct set by the printer device driver weren't being validated and could have resulted in invalid values which in turn would cause the browser to attempt out of bounds access to related variables.<br>*This bug only affects Firefox on Windows. Other operating systems are unaffected.*. This vulnerability affects Firefox < 110, Thunderbird < 102.8, and Firefox ESR < 102.8.
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 confidenceFirefox on Windows fails to validate DEVMODEW struct members set by printer device drivers, allowing invalid values to cause out-of-bounds memory access. This is a memory safety vulnerability in the printer driver handling code that only affects Windows platforms.
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< 110.0< 102.8< 102.8CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 your Firefox or Thunderbird versionIn Firefox: Menu > Help > About Firefox. In Thunderbird: Menu > Help > About Thunderbird. Note the version number displayed.Affected if The version is below 110.0 for Firefox, below 102.8 for Firefox ESR, or below 102.8 for Thunderbird.
-
Confirm you are running WindowsCheck your operating system. This vulnerability only affects Windows platforms. On macOS or Linux, you are not affected regardless of version.Affected if You are running any version of Firefox or Thunderbird on Windows.
-
Identify if you have used printer functionalityCheck for recent printed documents or print jobs from Firefox or Thunderbird. Look in your print spooler or recent documents. The vulnerability triggers when a printer device driver returns an invalid DEVMODEW struct.Affected if You have printed from Firefox or Thunderbird on Windows while running an affected version.
You are affected only if you run Firefox < 110.0, Firefox ESR < 102.8, or Thunderbird < 102.8 on Windows and have used the print 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 · scoped102.8110.0
Upgrade to Firefox 110+, Thunderbird 102.8+, or Firefox ESR 102.8+ to implement proper validation of printer driver DEVMODEW struct values.
Firefox 110.0, Firefox ESR 102.8, or Thunderbird 102.8
- For Firefox on Windows: Download and install Firefox 110.0 or later from mozilla.org
- For Firefox ESR on Windows: Download and install Firefox ESR 102.8 or later from mozilla.org
- For Thunderbird on Windows: Download and install Thunderbird 102.8 or later from mozilla.org
- Restart the browser/application after installation
- Verify the installed version by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-25738 — 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-2023-25738 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