CVE-2025-14237
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 · uneditedBuffer overflow in XPS font parse processing on Small Office Multifunction Printers and Laser Printers(*) which may allow an attacker on the network segment to trigger the affected product being unresponsive or to execute arbitrary code. *: Satera LBP670C Series/Satera MF750C Series firmware v06.02 and earlier sold in Japan.Color imageCLASS LBP630C/Color imageCLASS MF650C Series/imageCLASS LBP230 Series/imageCLASS X LBP1238 II/imageCLASS MF450 Series/imageCLASS X MF1238 II/imageCLASS X MF1643i II/imageCLASS X MF1643iF II firmware v06.02 and earlier sold in US.i-SENSYS LBP630C Series/i-SENSYS MF650C Series/i-SENSYS LBP230 Series/1238P II/1238Pr II/i-SENSYS MF450 Series/i-SENSYS MF550 Series/1238i II/1238iF II/imageRUNNER 1643i II/imageRUNNER 1643iF II firmware v06.02 and earlier sold in Europe.
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 buffer overflow vulnerability exists in the XPS font parsing component of multiple Canon printer firmware versions v06.02 and earlier. When processing maliciously crafted XPS font data, the parser fails to properly validate input buffer sizes before copying data, leading to memory corruption. An attacker on the same network segment can exploit this to cause device unresponsiveness (DoS) or achieve arbitrary code execution with elevated privileges.
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<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02CVSS 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.1/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 your Canon printer modelLocate the model number on the printer label or front panel. Common locations include the top front, inside the front door, or the rear label. Confirm it matches one of the affected models: MF455dw, MF453dw, MF452dw, MF451dw, MF654cdw, MF656cdw, MF653cdw, or MF652cw.Affected if The printer model is NOT one of the eight listed models - you are not affected by this specific CVE.
-
Check the installed firmware versionAccess the printer web interface by entering its IP address in a browser, then navigate to the Settings or Device Information section to view the firmware version. Alternatively, check via the printer control panel under Device Settings or About Device. Compare the version number to the affected range.Affected if Firmware version is GREATER than 06.02 (for example, 06.03 or later) - you are not affected. If version is 06.02 or earlier, you ARE affected.
-
Verify XPS printing capability is accessibleCheck the printer web interface or control panel for XPS print job support settings. Look for XPS printing in the features list or print settings. Determine if the XPS feature is enabled or if the printer accepts XPS document input.Affected if XPS printing is DISABLED and the printer does not accept XPS jobs - the attack surface may be reduced, but the vulnerability in the parser code still exists in unpatched firmware.
You are affected if your printer model is one of the eight listed Canon models AND the firmware version is 06.02 or earlier, regardless of whether you actively use XPS printing.
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 · scopedUpdate affected Canon printer firmware to version v06.02 or later as provided by Canon. Additionally, isolate printer devices on restricted network segments and disable XPS printing if not required to reduce attack surface.
Firmware version newer than v06.02 (e.g., v06.03 or later)
- Identify the specific Canon printer model from the affected product list
- Determine the current firmware version of the device through the printer control panel or web interface
- Download the latest firmware from the official Canon support website for your specific region and model
- Access the device administration panel via web browser using the printer's IP address
- Navigate to the firmware update section in the settings menu
- Upload and apply the downloaded firmware update file
- Verify the firmware version has been updated after the process completes
- Restart the device to ensure the update is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14237 — 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-2025-14237 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