# CVE-2019-6318: Code injection in HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers

> Insufficient signature validation in HP Enterprise printers allows attackers to execute arbitrary code on the device.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-99g5-79vp-5jv9

## What is CVE-2019-6318?

CVE-2019-6318 is a critical code injection vulnerability in HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers, published on 11 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers have an insufficient solution bundle signature validation that potentially allows execution of arbitrary code.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2019-6318?

It affects 143 products.


Products: Hp Color Laserjet Cm4540 Mfp Firmware, Hp Color Laserjet Enterprise Cp5525 Firmware, Hp Color Laserjet Enterprise Flow Mfp M577 Firmware, Hp Color Laserjet Enterprise Flow Mfp M680 Firmware, Hp Color Laserjet Enterprise Flow Mfp M681 Firmware, Hp Color Laserjet Enterprise Flow Mfp M682 Firmware, Hp Color Laserjet Enterprise Flow Mfp M880z Firmware, Hp Color Laserjet Enterprise M552 Firmware, Hp Color Laserjet Enterprise M553 Firmware, Hp Color Laserjet Enterprise M651 Firmware, Hp Color Laserjet Enterprise M652 Firmware, Hp Color Laserjet Enterprise M653 Firmware, Hp Color Laserjet Enterprise M750 Firmware, Hp Color Laserjet Enterprise M855 Firmware, Hp Color Laserjet Enterprise Mfp M577 Firmware, Hp Color Laserjet Enterprise Mfp M680 Firmware, Hp Color Laserjet Enterprise Mfp M681 Firmware, Hp Color Laserjet Enterprise Mfp M682 Firmware, Hp Color Laserjet Managed E55040dw Firmware, Hp Color Laserjet Managed E65050 Firmware and 123 more.

## How do I fix CVE-2019-6318?

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

## Is CVE-2019-6318 being exploited?

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

## Other vulnerabilities in HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers

- [CVE-2018-5923](https://insights.sbomify.com/CVE-2018-5923/): Code injection in HP LaserJet Enterprise, HP PageWide Enterprise, HP LaserJet Managed, and HP OfficeJet Enterprise Printers (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6318 and fix it if it is affected.

What it is: CVE-2019-6318 is a critical code injection vulnerability in HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers, published on 11 Apr 2019. 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-2019-6318 in the wild and no public exploit code.

Affected product: HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise 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-2019-6318/ (Markdown: https://insights.sbomify.com/CVE-2019-6318/index.md)
```

## Sources

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

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