CVE-2025-1004
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 printers may potentially experience a denial of service when a user sends a raw JPEG file to the printer via IPP (Internet Printing Protocol).
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 confidenceCertain HP LaserJet Pro printers can enter a denial of service condition when processing a raw JPEG file sent via IPP (Internet Printing Protocol). The printer fails to properly handle the malformed or specially crafted JPEG data through the IPP print service, causing it to become unresponsive or crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2024-10-25< 2024-10-25< 2024-10-25< 2024-10-25< 2024-10-25< 2024-10-25< 2024-10-25< 2024-10-25CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 printer modelAccess the printer's embedded web server (EWS) via its IP address, or print a configuration/status page from the printer control panel. Locate the product code/model number in the device information section.Affected if The product code matches one of the following: G3q78a, G3q79a, Q3q75a, G3q74a, G3q77a, G3q76a, 4pa41a, or 4pa42a
-
Check firmware versionIn the printer's EWS, navigate to the General or Firmware Information page. Alternatively, print a configuration page from the control panel and locate the firmware date or version string.Affected if The firmware date is earlier than 2024-10-25, or the version string indicates a build prior to that date.
-
Verify IPP service statusIn the printer's EWS, go to the Network Settings, Networking, or Services section. Look for IPP (Internet Printing Protocol) or the HP Jetdirect category. Confirm whether IPP is listed as enabled or active.Affected if IPP is enabled and accessible over the network. If IPP is disabled, the attack surface is reduced.
Your printer is affected if it matches one of the listed product codes, runs firmware dated before 2024-10-25, and has IPP enabled.
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.
dbcve · scoped2024-10-25
Network segment printers from general network access and restrict IPP functionality to authorized print servers. Apply vendor firmware updates when available and consider disabling IPP if not required, falling back to standard print protocols.
Firmware version 2024-10-25 or later for affected HP LaserJet Pro models
- 1. Identify your HP LaserJet Pro printer model from the affected list (G3q78a, G3q79a, Q3q75a, G3q74a, G3q77a, G3q76a, 4pa41a, or 4pa42a).
- 2. Check the current firmware version on your printer by printing a configuration page or accessing the printer's embedded web server.
- 3. Navigate to support.hp.com and enter your specific printer model to locate the firmware download section.
- 4. Download the firmware update dated 2024-10-25 or later.
- 5. Apply the firmware update using HP Web JetAdmin, the printer's embedded web server, or HP Smart app following HP's standard firmware update procedure.
- 6. After updating, verify the new firmware version displays 2024-10-25 or later on the configuration page.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1004 — 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-2025-1004 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