CVE-2025-14231
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 print job processing by WSD 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 WSD (Web Services for Devices) print job processing component of Canon Satera, Color imageCLASS, i-SENSYS, and imageRUNNER printer devices. Attackers on the same network segment can send malicious print jobs via WSD that overflow a buffer, potentially causing device unresponsiveness (denial of service) or enabling 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 printer modelAccess the printer's web interface or print a configuration page to confirm the exact model name (e.g., LBP1238 II, LBP632CDW, MF1643i II, etc.)Affected if The model matches one of the affected products: Canon LBP1238 II, LBP632CDW, LBP633CDW, LBP236DW, LBP237DW, MF1643i II, MF1643if II, or MF1238 II
-
Check installed firmware versionVia the printer's web interface (typically under Settings or Device Information), or print a configuration/test page that displays firmware versionAffected if Firmware version is 06.02 or lower (any version <= 06.02)
-
Verify WSD service statusAccess the printer's web interface and navigate to Network Settings or Services configuration to check if Web Services for Devices (WSD) is enabledAffected if WSD is enabled and accessible on the network
-
Assess network accessibility of WSD portUse a network scanner or nmap to check if ports 80/8000 (common WSD ports) are open and reachable from your network segment; verify printer is on the same network segment as untrusted usersAffected if The printer's WSD service is reachable from network segments that contain untrusted or guest devices
You are affected if your Canon printer model matches one of the listed products, runs firmware version 06.02 or lower, and has WSD enabled and network-accessible.
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 printer firmware to a version newer than v06.02; if immediate patching is not feasible, restrict network access to WSD services via firewall rules or disable WSD functionality if not required, and place printers in an isolated network segment.
Firmware version newer than v06.02 (check Canon support for the specific fixed version for your model)
- 1. Identify the exact Canon printer model from the affected product list
- 2. Access the Canon support website for your region (canon.jp, canon-europe.com, usa.canon.com, or psirt.canon)
- 3. Navigate to the drivers and downloads section for your specific printer model
- 4. Download the latest firmware version available (must be newer than v06.02)
- 5. Follow Canon's official firmware update instructions, typically involving: connecting the printer via USB or network, accessing the printer's web interface or using the Canon firmware update utility
- 6. Verify the firmware update was successful by checking the firmware version in the printer's web interface or control panel
- 7. As a defensive measure, consider disabling the WSD (Web Services on Devices) protocol in the printer settings if not required for business needs
- 8. Ensure the printer is placed behind a firewall or VLAN to limit network exposure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.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 $7,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14231 — 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-14231 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