CVE-2023-35175
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 Potential Remote Code Execution and/or Elevation of Privilege via Server-Side Request Forgery (SSRF) using the Web Service Eventing model.
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 SSRF vulnerability in the Web Service Eventing model that allows remote attackers to potentially execute arbitrary code or elevate privileges. The vulnerability is network-exploitable and rated critical due to the potential for complete system compromise.
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
- 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 model numberAccess the printer's embedded web server (EWS) by entering the printer's IP address in a web browser, then navigate to the General or Information page to locate the product number. Alternatively, print a configuration page from the printer control panel to find the model identifier.Affected if The model number matches one of: W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, or W1a82a
-
Check the installed firmware versionIn the printer's embedded web server, go to the General or Information tab and locate the Firmware Revision or Firmware Version field. Compare this version to the affected range.Affected if The firmware version is earlier than 002_2322c (for example, 002_2319a, 002_2305b, etc.)
-
Verify Web Service Eventing is accessibleCheck if the printer's web interface exposes the Web Service Eventing endpoint. This is typically found under Web Services or Eventing settings in the EWS. You can also attempt to access the WSDL endpoint at /eventing/EventService.wsdl on the printer's IP.Affected if The Web Service Eventing feature is enabled and the endpoint is accessible over the network (ports 80 or 443)
-
Confirm network accessibility of the printer management interfaceAttempt to reach the printer's embedded web server from a remote system using its IP address on HTTP/HTTPS ports. Verify if the interface is exposed beyond the local network.Affected if The printer's web management interface is reachable from untrusted network segments or the internet
You are affected if you have an HP LaserJet Pro model W1a75a through W1a82a running firmware version below 002_2322c with the Web Service Eventing feature accessible over the network.
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
Apply vendor firmware updates when available, disable unused web services on affected printers, and restrict network access to printer management interfaces via firewall rules or network segmentation.
Firmware version 002_2322c or later
- Identify your specific HP LaserJet Pro model number (W1a75a through W1a82a) from the printer display or label
- Navigate to HP Support (support.hp.com) and locate the firmware download page for your specific model
- Download firmware version 002_2322c or later from HP's official support site
- Access the printer's embedded web server (EWS) by entering the printer's IP address in a web browser
- Log into the EWS with administrator credentials
- Locate the Firmware Update section in the EWS (typically under General or Administration settings)
- Upload and apply the downloaded firmware file (.bdl or .fwu format)
- Allow the printer to complete the firmware update process (do not power off during update)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35175 — 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-35175 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