CVE-2024-2301
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 devices are potentially vulnerable to a Cross-Site Scripting (XSS) attack via the web management interface of the device.
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 confidenceCross-Site Scripting (XSS) vulnerability in the web management interface of certain HP LaserJet Pro devices allows attackers to inject malicious scripts through the interface, potentially compromising user sessions or executing arbitrary code in the context of the victim's browser.
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< 2023-03-30< 2023-03-30< 2023-03-30< 2023-03-30< 2023-03-30< 2023-03-30< 2023-03-30< 2023-03-30CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
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 device model and firmware codeAccess the printer's web management interface (typically http://[printer-ip] or https://[printer-ip]) and navigate to the General or Information page to view the product model and firmware code (such as Cz181a, Cz182a, Cz187a, Cz183a, Cz172a, Cz173a, Cz176a, or Cz177a). Alternatively, check the information page printed from the device control panel or query via SNMP.Affected if The device model displays one of the affected firmware codes: Cz181a, Cz182a, Cz187a, Cz183a, Cz172a, Cz173a, Cz176a, or Cz177a.
-
Check firmware version and dateIn the web management interface, locate the firmware version or build date information, typically found under General, Support, or About sections. This is often displayed as a date (YYYY-MM-DD format) or a version number with an associated date.Affected if The firmware build date is before 2023-03-30, or the version number corresponds to a build earlier than the March 30, 2023 release.
-
Confirm web management interface is accessibleAttempt to reach the printer's web interface by browsing to the printer's IP address on ports 80 or 443. Verify the interface loads and displays the login or status page.Affected if The web management interface is reachable and functional on the network.
A device is affected if it carries one of the specific firmware codes (Cz181a, Cz182a, Cz187a, Cz183a, Cz172a, Cz173a, Cz176a, Cz177a) with a build date earlier than 2023-03-30 and has its web management interface 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 · scoped2023-03-30
Apply the vendor-supplied firmware update or patch for affected HP LaserJet Pro devices. If no patch is available, consider network segmentation to limit access to the device management interface and implement additional input validation at the network perimeter.
Firmware version 2023-03-30 or later for HP LaserJet Pro Cz181a/Cz182a/Cz187a/Cz183a/Cz172a/Cz173a/Cz176a/Cz177a
- Access the printer's web management interface through its IP address
- Navigate to the firmware or administration section
- Check the current firmware version (should be pre-2023-03-30 for affected devices)
- Download the latest firmware update from HP support website for your specific model (Cz181a, Cz182a, Cz187a, Cz183a, Cz172a, Cz173a, Cz176a, or Cz177a)
- Upload and install the firmware update through the web interface or HP Smart app
- Verify the firmware has been updated to version 2023-03-30 or later
- Confirm the vulnerability is remediated by verifying the web management interface handles input properly
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2301 — 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-2301 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