CVE-2022-34886 json
A remote code execution vulnerability was found in the firmware used in some Lenovo printers, which can be caused by a remote user pushing…
published 2023-10-27 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-37790
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Lenovo Printer GM265DN (production date June 2022 and before) 01.00.20N
- Lenovo Printer GM265DN (production date July 2022 and later) 01.17.00.03.00
- Lenovo Printer GM266DNS 02.06.00.04.00
- Lenovo Printer G263DNS 02.06.00.04.00
- lenovo gm265dn_firmware 01.00.20N, 01.17.00.03.00
- lenovo gm266dns_firmware 02.06.00.04.00
- lenovo g263dns_firmware 02.06.00.04.00
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Lenovo Printer GM265DN (production date June 2022 and before)
- Lenovo Printer GM265DN (production date July 2022 and later)
- Lenovo Printer GM266DNS
- Lenovo Printer G263DNS
- lenovo gm265dn_firmware
- lenovo gm266dns_firmware
- lenovo g263dns_firmware
Classification
References
-
iknow.lenovo.com.cn
/detail/205041.html
patch, vendor-advisory
Sources
- CVE List CVE-2022-34886
- NVD CVE-2022-34886
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.