# CVE-2024-3286: Memory corruption in Printers

> An unauthenticated attacker can trigger a device restart on Lenovo printers via a buffer overflow in a web request.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2024
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-3xrh-q6h2-52xr

## What is CVE-2024-3286?

CVE-2024-3286 is a high-severity memory corruption vulnerability in Lenovo Printers, published on 16 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow vulnerability was identified in some Lenovo printers that could allow an unauthenticated user to trigger a device restart by sending a specially crafted web request.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-3286?


## How do I fix CVE-2024-3286?

No fix has been published for CVE-2024-3286 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3286 being exploited?

There is no known exploitation of CVE-2024-3286 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3286 and fix it if it is affected.

What it is: CVE-2024-3286 is a high-severity memory corruption vulnerability in Lenovo Printers, published on 16 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3286 in the wild and no public exploit code.

Affected product: Lenovo Printers. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3286/ (Markdown: https://insights.sbomify.com/CVE-2024-3286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3286
- OSV: https://osv.dev/vulnerability/CVE-2024-3286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3286/
Summaries are generated and may contain mistakes; the official description above is the record.