CVE-2023-35177
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 a stack-based buffer overflow related to the compact font format parser.
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 confidenceA stack-based buffer overflow vulnerability exists in the compact font format parser of certain HP LaserJet Pro print products. An attacker could exploit this by sending specially crafted font data to the printer, potentially leading to remote code execution or denial of service conditions.
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 model codePrint a configuration page from the printer or access the embedded web server (EWS) via the printer's IP address to locate the product number (model number) - look for codes such as W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, or W1a82aAffected if The printer model matches one of these eight product codes
-
Check the installed firmware versionAccess the printer's embedded web server and navigate to the 'General' or 'Information' page, or print a configuration/configuration page from the printer's control panel to locate the firmware version fieldAffected if The firmware version is below 002_2322c (for example, 002_2319a, 002_2305b, etc.)
-
Verify the compact font feature is accessibleConfirm the printer is network-connected and accepts print jobs - the vulnerability is in the compact font format parser which processes font data sent via print jobsAffected if The printer accepts print jobs from network sources (even if only from trusted internal networks)
A user is affected if their HP LaserJet Pro printer has model code W1a75a through W1a82a and is running firmware version 002_2322c or lower.
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-supplied firmware updates for affected HP LaserJet Pro devices when released, and implement network segmentation to limit printer exposure to untrusted networks.
Firmware version 002_2322c or later for W1a75a-W1a82a LaserJet Pro models
- Visit HP Support website at support.hp.com and navigate to your printer model (W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, or W1a82a)
- Locate the firmware download section for your specific printer model
- Download the firmware version 002_2322c or later
- Connect the printer to your computer via USB or network
- Access the printer's embedded web server (EWS) by entering the printer's IP address in a web browser
- Navigate to the 'Firmware Update' or 'General' settings section in EWS
- Upload and install the downloaded firmware file
- Wait for the firmware update to complete - do not power off the printer during the 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-35177 — 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-35177 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