CVE-2023-35176
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 and/or Denial of Service when using the backup & restore feature through the embedded web service on 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 confidenceHP LaserJet Pro printers contain a buffer overflow and denial of service vulnerability in the backup and restore functionality of the embedded web server (EWS). An attacker with network access to the device's web interface can potentially execute arbitrary code or cause the device to become unavailable.
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 your printer modelCheck the product label on the printer or access the EWS homepage. Look for the model number (W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, or W1a82a).Affected if The model number matches one of the eight affected product codes.
-
Check the installed firmware versionAccess the EWS at the printer's IP address, navigate to the General or About page, and locate the firmware version field. Alternatively, print a configuration page from the printer control panel.Affected if The firmware version is lower than 002_2322c (for example, 002_2319a or earlier).
-
Verify the EWS is accessibleOpen a web browser and navigate to http://[printer-ip-address]. Confirm the HP LaserJet Pro login page loads.Affected if The embedded web server is reachable over the network.
-
Confirm backup and restore feature existsLog into the EWS and look for a Backup/Restore, Settings, or General menu option. This feature is present in most LaserJet Pro models.Affected if The backup and restore functionality is available in the web interface.
You are affected if your printer model is W1a75a through W1a82a, firmware version is below 002_2322c, and the EWS is network-accessible with the backup/restore feature present.
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
Restrict network access to the printer's embedded web server, disable the feature if not needed, and apply HP firmware updates when available. Consider network segmentation to isolate printer traffic.
HP LaserJet Pro firmware version 002_2322c or later
- 1. Identify the exact HP LaserJet Pro model number (W1a75a through W1a82a) from the device label or control panel
- 2. Access the HP support website at support.hp.com and navigate to the drivers and downloads section for your specific model
- 3. Download the latest firmware version 002_2322c or later for your device model
- 4. Access the printer's embedded web server (EWS) by entering the printer's IP address in a web browser
- 5. Log into the EWS with administrator credentials
- 6. Navigate to the 'General' or ' firmware' settings section
- 7. Select the option to update firmware and upload the downloaded firmware file (.bdl or .bin)
- 8. Wait for the firmware upload and installation to complete - do not power off the printer during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35176 — 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-35176 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