IM C3510/C3010: Out-of-bounds Write
CVE-2024-39927 is a high-severity out-of-bounds write vulnerability in IM C3510/C3010 from Ricoh Company, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected IM C3510/C3010 versions: prior to System/Copy 2.00-00. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.58% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update im_c3510 to system\/copy_2.00-00 or a later version.
- Update im_c3010 to system\/copy_2.00-00 or a later version.
- Update im_c6010 to system\/copy_2.00-00 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ricoh Company | IM C3510/C3010 | prior to System/Copy 2.00-00 | Not stated |
| Ricoh Company | IM C6010/C5510/C4510 | prior to System/Copy 2.00-00 | Not stated |
| Ricoh Company | IM C2510/C2010 | prior to System/Copy 2.00-00 | Not stated |
| Ricoh Company | IM C7010 | prior to System/Copy 1.05-00 | Not stated |
| Ricoh Company | IM 460F/460FTL/370/370F | prior to System/Copy 1.10-00 | Not stated |
| Ricoh Company | IM C8500/C8510M/C8500/C8500M | prior to System 1.04-00 | Not stated |
| Ricoh | im_c3510 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c3010 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c6010 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c5510 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c4510 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c2510 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c2010 | before system\/copy_2.00-00 | system\/copy_2.00-00 |
| Ricoh | im_c7010 | before system\/copy_1.05-00 | system\/copy_1.05-00 |
| Ricoh | im_460f | before system\/copy_1.10-00 | system\/copy_1.10-00 |
| Ricoh | im_460ftl | before system\/copy_1.10-00 | system\/copy_1.10-00 |
| Ricoh | 370 | before system\/copy_1.10-00 | system\/copy_1.10-00 |
| Ricoh | 370f | before system\/copy_1.10-00 | system\/copy_1.10-00 |
| Ricoh | im_c8500 | before system\/copy_1.04-00 | system\/copy_1.04-00 |
| Ricoh | im_c8510m | before system\/copy_1.04-00 | system\/copy_1.04-00 |
| Ricoh | im_c8500m | before system\/copy_1.04-00 | system\/copy_1.04-00 |
Version data comes from the organisation that assigned the CVE. 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
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H. Scored by CISA (ADP).
Official description
Out-of-bounds write vulnerability exists in Ricoh MFPs and printers. If a remote attacker sends a specially crafted request to the affected products, the products may be able to cause a denial-of-service (DoS) condition and/or user's data may be destroyed.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.0 High severity
- 7.5 High severity
- 8.2 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.