CVE-2024-0794
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain HP LaserJet Pro, HP Enterprise LaserJet, and HP LaserJet Managed Printers are potentially vulnerable to Remote Code Execution due to buffer overflow when rendering fonts embedded in a PDF file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer overflow vulnerability in HP LaserJet printers allows remote code execution when processing maliciously crafted PDF files with embedded fonts. The vulnerability stems from insufficient bounds checking during font rendering, enabling an attacker to overflow the buffer and execute arbitrary code on the affected device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the printer modelAccess the printer's web interface or control panel and locate the device information or about page to confirm it is an HP LaserJet printer. Alternatively, print a configuration page from the control panel.Affected if The device is not an HP LaserJet printer model, as this vulnerability only affects HP LaserJet devices.
-
Determine the installed firmware versionAccess the printer's web interface (typically via IP address), navigate to the General or About section, and record the firmware version. Alternatively, print a configuration page from the control panel which usually lists the firmware version.Affected if The firmware version cannot be determined or is older than the HP-provided patched firmware version for this CVE.
-
Check if PDF printing is enabledReview the printer's web interface or control panel settings for print job processing. Look for PDF print job acceptance settings or IPP/SMB print queue configurations that accept PDF documents.Affected if PDF print job processing is enabled and the printer accepts PDF files from network sources.
-
Assess network exposureReview network firewall rules and printer IP address configuration. Determine if the printer is directly accessible from untrusted networks or if print services are exposed to the internet.Affected if The printer is accessible from untrusted network segments or the internet without network isolation.
You are affected if you have an HP LaserJet printer with firmware lacking the CVE-2024-0794 patch that processes PDF print jobs from network sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply HP-provided firmware updates to affected printer models when released; in the interim, network isolate affected printers and restrict PDF file processing from untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data