Printer GM265DN (production date June 2022 and…: Out-of-bounds Write
CVE-2022-34886 is a high-severity out-of-bounds write vulnerability in Printer GM265DN (production date June 2022 and before) from Lenovo, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 01.00.20N as the first without the flaw, so updating Printer GM265DN (production date June 2022 and before) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.08% chance of exploitation within 30 days, higher than 66% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Printer GM265DN (production date June 2022 and before) to 01.00.20N or a later version.
- Update Printer GM265DN (production date July 2022 and later) to 01.17.00.03.00 or a later version.
- Update Printer GM266DNS to 02.06.00.04.00 or a later version.
- Read the advisory on iknow.lenovo.com.cn for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Lenovo | Printer GM265DN (production date June 2022 and before) | before 01.00.20N | 01.00.20N |
| Lenovo | Printer GM265DN (production date July 2022 and later) | before 01.17.00.03.00 | 01.17.00.03.00 |
| Lenovo | Printer GM266DNS | before 02.06.00.04.00 | 02.06.00.04.00 |
| Lenovo | Printer G263DNS | before 02.06.00.04.00 | 02.06.00.04.00 |
| Lenovo | gm265dn_firmware | before 01.00.20N; before 01.17.00.03.00 | 01.00.20N, 01.17.00.03.00 |
| Lenovo | gm266dns_firmware | before 02.06.00.04.00 | 02.06.00.04.00 |
| Lenovo | g263dns_firmware | before 02.06.00.04.00 | 02.06.00.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
- LowA basic user account is enough.
- 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:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (lenovo.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
A remote code execution vulnerability was found in the firmware used in some Lenovo printers, which can be caused by a remote user pushing an illegal string to the server-side interface via a script, resulting in a stack overflow.
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: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Recent Out-of-bounds Write vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.