# CVE-2023-35176: Memory corruption in HP LaserJet Pro

> Attackers can exploit a buffer overflow in the backup and restore feature of HP LaserJet Pro printers to execute code or cause denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2023
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-m887-p4fp-j734

## What is CVE-2023-35176?

CVE-2023-35176 is a high-severity memory corruption vulnerability in HP LaserJet Pro, published on 30 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain HP LaserJet Pro print products are potentially vulnerable to Buffer Overflow and/or Denial of Service when using the backup & restore feature through the embedded web service on the device.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-35176?

It affects 38 products.


Products: Hp Laserjet Pro M304-M305 W1a46a Firmware, Hp Laserjet Pro M304-M305 W1a47a Firmware, Hp Laserjet Pro M304-M305 W1a48a Firmware, Hp Laserjet Pro M304-M305 W1a66a Firmware, Hp Laserjet Pro M404-M405 93m22a Firmware, Hp Laserjet Pro M404-M405 W1a51a Firmware, Hp Laserjet Pro M404-M405 W1a52a Firmware, Hp Laserjet Pro M404-M405 W1a53a Firmware, Hp Laserjet Pro M404-M405 W1a56a Firmware, Hp Laserjet Pro M404-M405 W1a57a Firmware, Hp Laserjet Pro M404-M405 W1a58a Firmware, Hp Laserjet Pro M404-M405 W1a59a Firmware, Hp Laserjet Pro M404-M405 W1a60a Firmware, Hp Laserjet Pro M404-M405 W1a63a Firmware, Hp Laserjet Pro M453-M454 W1y40a Firmware, Hp Laserjet Pro M453-M454 W1y41a Firmware, Hp Laserjet Pro M453-M454 W1y43a Firmware, Hp Laserjet Pro M453-M454 W1y44a Firmware, Hp Laserjet Pro M453-M454 W1y45a Firmware, Hp Laserjet Pro M453-M454 W1y46a Firmware and 18 more.

## How do I fix CVE-2023-35176?

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

## Is CVE-2023-35176 being exploited?

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

## Other vulnerabilities in HP LaserJet Pro

- [CVE-2023-35175](https://insights.sbomify.com/CVE-2023-35175/): Server-side request forgery in HP LaserJet Pro (critical 9.8)
- [CVE-2023-27971](https://insights.sbomify.com/CVE-2023-27971/): Memory corruption in HP LaserJet Pro (critical 9.8)
- [CVE-2023-27972](https://insights.sbomify.com/CVE-2023-27972/): Memory corruption in HP LaserJet Pro (critical 9.8)
- [CVE-2023-27973](https://insights.sbomify.com/CVE-2023-27973/): Memory corruption in HP LaserJet Pro (critical 9.8)
- [CVE-2022-24292](https://insights.sbomify.com/CVE-2022-24292/): Other in HP LaserJet Pro Printers; HP Pagewide Pro Printers; HP Officejet Printers (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35176 and fix it if it is affected.

What it is: CVE-2023-35176 is a high-severity memory corruption vulnerability in HP LaserJet Pro, published on 30 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35176 in the wild and no public exploit code.

Affected product: HP LaserJet Pro. 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-2023-35176/ (Markdown: https://insights.sbomify.com/CVE-2023-35176/index.md)
```

## Sources

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

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