CyberSecBulletin
CVE-2024-2184NVD status: Deferred

Color imageCLASS MF740C Series: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-2184 is a critical-severity out-of-bounds write vulnerability in Color imageCLASS MF740C Series from Canon, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Color imageCLASS MF740C Series versions: v12.07 and earlier; 12..07 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.81% chance of exploitation within 30 days, higher than 58% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of Color imageCLASS MF740C Series you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on psirt.canon for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
CanonColor imageCLASS MF740C Seriesv12.07 and earlier; 12..07 and earlierNot stated
CanonColor imageCLASS MF640C Seriesv12.07 and earlier; 12.07 and earlierNot stated
Canoni-SENSYS MF740C Seriesv12.07 and earlier; 12.07 and earlierNot stated
Canoni-SENSYS MF640C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonSatera MF740C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonSatera MF640C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonColor imageCLASS X MF1127Cv12.07 and earlier; 12.07 and earlierNot stated
CanonC1127i Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonColor imageCLASS LBP664Cdwv12.07 and earlier; 12.07 and earlierNot stated
CanonColor imageCLASS LBP622Cdwv12.07 and earlier; 12.07 and earlierNot stated
Canoni-SENSYS LBP660C Seriesv12.07 and earlier; 12.07 and earlierNot stated
Canoni-SENSYS LBP620C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonSatera LBP660C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonSatera LBP620C Seriesv12.07 and earlier; 12.07 and earlierNot stated
CanonColor imageCLASS X LBP1127Cv12.07 and earlier; 12.07 and earlierNot stated
CanonC1127Pv12.07 and earlier; 12.07 and earlierNot stated
CanonColor imageCLASS MF750C Seriesv03.09 and earlier; 03.09 and earlierNot stated
Canoni-SENSYS MF750C Seriesv03.09 and earlier; 03.09 and earlierNot stated
CanonSatera MF750C Seriesv03.09 and earlier; 03.09 and earlierNot stated
CanonColor imageCLASS X MF1333Cv03.09 and earlier; 03.09 and earlierNot stated
CanonC1333i Seriesv03.09 and earlier; 03.09 and earlierNot stated
CanonColor imageCLASS LBP674Cdwv03.09 and earlier; 03.09 and earlierNot stated
Canoni-SENSYS LBP673Cdwv03.09 and earlier; 03.09 and earlierNot stated
CanonSatera LBP670C Seriesv03.09 and earlier; 03.09 and earlierNot stated
CanonColor imageCLASS X LBP1333Cv03.09 and earlier; 03.09 and earlierNot stated

Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.