CVE-2023-35178
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 print products are potentially vulnerable to Buffer Overflow when performing a GET request to scan jobs.
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 confidenceHP LaserJet Pro print products contain a buffer overflow vulnerability in the scan jobs handling functionality. A crafted GET request to the scan jobs endpoint can trigger a buffer overflow, potentially allowing remote code execution or denial of service.
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< 002_2322c< 002_2322c< 002_2322c< 002_2322c< 002_2322c< 002_2322c< 002_2322c< 002_2322cCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelCheck the product label or access the printer's web interface (usually via IP address) to confirm the exact model number matches one of: W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, W1a82aAffected if The model is one of the eight listed product numbers
-
Check the installed firmware versionAccess the printer web interface and navigate to the General or About page, or print a configuration page from the control panel, to find the firmware version stringAffected if The firmware version is earlier than 002_2322c (for example, 002_2319a or lower)
-
Verify scan service is enabledCheck the printer settings via the web interface or control panel to see if scan-to-email, scan-to-network, or scan jobs functionality is turned onAffected if Scan jobs handling is enabled and the device is accessible on the network
-
Confirm network accessibility of the web interfaceAttempt to access the printer's HTTP management interface from a remote host using the IP address, or check firewall rules allowing HTTP/HTTPS to the printerAffected if The scan jobs endpoint (typically /scan/jobs or similar path) is reachable over the network
The device is affected if it is one of the eight listed HP LaserJet Pro models, has firmware version lower than 002_2322c, and has scan jobs functionality enabled with network accessibility.
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 · scoped002_2322c
Update HP LaserJet Pro firmware to the latest version. If no patch is available, restrict network access to printer management interfaces and disable unnecessary scan services.
HP LaserJet Pro firmware version 002_2322c or later for models W1a75a through W1a82a
- Identify the specific HP LaserJet Pro model number (W1a75a through W1a82a) from the printer control panel or label
- Access the printer's embedded web server by entering its IP address in a web browser
- Navigate to the Firmware Update or Administration section to check the current firmware version
- Confirm the current firmware version is below 002_2322c
- Download the firmware update version 002_2322c or later from HP support website (support.hp.com) for your specific model
- Upload and apply the firmware update through the printer's web interface or USB connection following HP's documented update procedure
- After the update completes, verify the firmware version has been updated to 002_2322c or later via the web interface or control panel
- Restart the printer to ensure the new firmware loads properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35178 — 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-2023-35178 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