dbcve.org
D1620 FirmwareOperating system · Canon

CVE-2022-24672

HIGH · 8.8 CVSS v3.1 Published 2023-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Canon imageCLASS MF644Cdw 10.02 printers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the CADM service. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-15802.

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

Heap-based buffer overflow in the CADM service of Canon imageCLASS MF644Cdw printers (firmware 10.02) allows unauthenticated network-adjacent attackers to execute arbitrary code via improper length validation of user-supplied data before copying to a fixed-length heap buffer.

MitigationApply vendor firmware update when available; until then, restrict network access to the printer and disable unnecessary services to reduce attack surface.

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
D1620 FirmwareOperating system
Affected:all versions
D1650 FirmwareOperating system
Affected:all versions
D1520 FirmwareOperating system
Affected:all versions
D1550 FirmwareOperating system
Affected:all versions
Mf1127c FirmwareOperating system
Affected:all versions
Mf1238 FirmwareOperating system
Affected:all versions
Mf1238 Ii FirmwareOperating system
Affected:all versions
Mf1643i Ii FirmwareOperating system
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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
    Check the printer model by accessing the web interface, printing a configuration page, or checking the device label. Look for: D1620, D1650, D1520, D1550, Mf1127c, Mf1238, Mf1238 Ii, or Mf1643i Ii.
    Affected if The printer model matches one of the affected models listed in the CVE.
  2. Verify CADM service status
    Access the printer web interface (http://<printer-ip>) and navigate to Settings or Security settings. Look for CADM (Canon Advanced Document Manager) service or similar document service settings. Alternatively, check via SNMP or the printer's embedded web server for enabled services.
    Affected if The CADM service is enabled on the printer.
  3. Check network exposure of the CADM service
    Determine if the printer is on a restricted network segment or directly exposed. Use nmap or similar tool to check if the CADM-related ports (commonly 80, 443, or vendor-specific HTTP ports) are accessible from untrusted network segments. Review VLAN configurations and firewall rules around the printer.
    Affected if The CADM service is accessible from network-adjacent attackers without authentication barriers.
  4. Confirm firmware version
    Print a configuration page or access the printer's system settings via the web interface to view the installed firmware version.
    Affected if The firmware version is any version on the affected models - all versions are listed as vulnerable.

A user is affected if their printer model is one of the listed affected models, the CADM service is enabled, and the service is accessible to unauthenticated network-adjacent attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update when available; until then, restrict network access to the printer and disable unnecessary services to reduce attack surface.

Fix this in D1620 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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