CVE-2024-45320
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 · uneditedOut-of-bounds write vulnerability exists in DocuPrint CP225w 01.22.01 and earlier, DocuPrint CP228w 01.22.01 and earlier, DocuPrint CM225fw 01.10.01 and earlier, and DocuPrint CM228fw 01.10.01 and earlier. If an affected MFP processes a specially crafted printer job file, a denial-of-service (DoS) condition may occur.
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 confidenceAn out-of-bounds write vulnerability exists in the firmware of multiple Fuji Xerox DocuPrint MFP models (CP225w, CP228w, CM225fw, CM228fw) when processing specially crafted printer job files. The vulnerability can cause memory corruption leading to a denial-of-service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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.
-
Identify the printer modelAccess the printer's web interface (usually by entering the printer's IP address in a browser) and check the device information or status page, or print a configuration page from the printer control panelAffected if The model is one of: CP225w, CP228w, CM225fw, or CM228fw
-
Check the installed firmware versionIn the printer web interface, navigate to the Firmware or Version information section (often under Settings, Maintenance, or Device Information). Alternatively, print a test page or configuration page from the control panel that displays firmware versionAffected if The firmware version is 01.22.01 or earlier for CP225w/CP228w, or 01.10.01 or earlier for CM225fw/CM228fw
-
Confirm print services are enabledIn the printer web interface, check the Network or Services settings to verify that print services (such as IPP, LPD, or raw TCP printing) are enabled. This is typically enabled by default on network MFPsAffected if Network printing services are enabled (this is the default and common configuration, making the device potentially reachable)
-
Verify network accessibility of the printerPing the printer's IP address or use a network scanner to confirm the printer is reachable on the network. Check if the printer's web interface port (usually 80 or 443) is accessible from network segmentsAffected if The printer is network-accessible and its web interface or print ports are reachable from user or guest network segments
A user is affected if they have a CP225w, CP228w, CM225fw, or CM228fw printer with firmware at or below the vulnerable version thresholds and the printer is network-accessible with print services enabled.
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.
From vendor dataUpdate the printer firmware to a version newer than 01.22.01 (for CP225w/CP228w) or 01.10.01 (for CM225fw/CM228fw). If firmware updates are unavailable, isolate printers on a restricted network segment and disable unnecessary print services.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45320 — 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-2024-45320 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