dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-2184

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Buffer overflow in identifier field of WSD probe request process of 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 MF740C Series/Satera MF640C Series/Satera LBP660C Series/Satera LBP620C Series firmware v12.07 and earlier, and Satera MF750C Series/Satera LBP670C Series firmware v03.09 and earlier sold in Japan.Color imageCLASS MF740C Series/Color imageCLASS MF640C Series/Color imageCLASS X MF1127C/Color imageCLASS LBP664Cdw/Color imageCLASS LBP622Cdw/Color imageCLASS X LBP1127C firmware v12.07 and earlier, and Color imageCLASS MF750C Series/Color imageCLASS X MF1333C/Color imageCLASS LBP674Cdw/Color imageCLASS X LBP1333C firmware v03.09 and earlier sold in US.i-SENSYS MF740C Series/i-SENSYS MF640C Series/C1127i Series/i-SENSYS LBP660C Series/i-SENSYS LBP620C Series/C1127P firmware v12.07 and earlier, and i-SENSYS MF750C Series/C1333i Series/i-SENSYS LBP673Cdw/C1333P firmware v03.09 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 confidence

Buffer overflow vulnerability in the identifier field of the WSD (Web Services on Devices) probe request processing in Canon Satera, Color imageCLASS, and i-SENSYS printer firmware. An attacker on the same network segment can send a specially crafted WSD probe request to cause the printer to become unresponsive or achieve arbitrary code execution.

MitigationUpdate affected printer firmware to v12.08 or later for MF740C/MF640C/LBP660C/LBP620C series, and v03.10 or later for MF750C/LBP670C series. As a compensating control, restrict network access to the WSD service by placing printers in an isolated network segment or VLAN.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify printer model and firmware version
    Access the printer's web interface or control panel to locate the model name and current firmware version. This is typically found in Settings or Maintenance sections.
    Affected if The printer is a Canon Satera, Color imageCLASS, or i-SENSYS model running firmware earlier than the fixed versions (v12.08 for MF740C/MF640C/LBP660C/LBP620C series, v03.10 for MF750C/LBP670C series).
  2. Confirm WSD service is enabled
    Check the printer's network settings or web interface for Web Services on Devices (WSD) status. This is usually found under Network Settings, Port Settings, or WSD Configuration.
    Affected if WSD service is currently enabled on the printer, as this is required for the specially crafted probe request to reach the vulnerable code path.
  3. Verify network exposure of WSD service
    Review network configuration to determine if the printer's WSD port (UDP port 3702) is accessible from network segments outside the trusted internal network.
    Affected if The WSD service is reachable from untrusted network segments, allowing an attacker on the same network to send the malicious probe request.

You are affected if you have a Canon Satera, Color imageCLASS, or i-SENSYS printer with WSD enabled running firmware older than the fixed versions and the WSD service is network-accessible to untrusted users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected printer firmware to v12.08 or later for MF740C/MF640C/LBP660C/LBP620C series, and v03.10 or later for MF750C/LBP670C series. As a compensating control, restrict network access to the WSD service by placing printers in an isolated network segment or VLAN.

Recommended fix Moderate confidence

Firmware version newer than v12.07 for MF740C/MF640C/LBP660C/LBP620C series, and newer than v03.09 for MF750C/LBP670C series (exact fixed version available from Canon security advisory)

  1. Check Canon's official support website (psirt.canon) or the Canon product security advisory for the latest firmware version for your specific printer model
  2. Identify your exact printer model number and current firmware version
  3. Download the firmware update from Canon's official support page for your region
  4. Follow Canon's firmware update instructions, typically involving accessing the printer's web interface or using the Canon firmware update utility
  5. After updating, verify the firmware version has been successfully changed to a version newer than v12.07 or v03.09 depending on your model series
  6. Confirm the WSD (Web Services on Devices) functionality is working properly after the update
Caveat Firmware updates may reset some printer settings; backup configuration if possible before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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