Color Laser 150 4zb94aHardware / appliance · Hp

CVE-2021-3438

HIGH · 7.8 CVSS v3.1 Published 2021-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A potential buffer overflow in the software drivers for certain HP LaserJet products and Samsung product printers could lead to an escalation of privilege.

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 confidence

A buffer overflow vulnerability exists in the software drivers for certain HP LaserJet and Samsung printers. This memory corruption issue in the printer driver can be exploited to achieve privilege escalation, potentially allowing an attacker to execute code with elevated system privileges.

MitigationApply available driver updates from HP or Samsung for affected LaserJet and Samsung printer models. If updates are unavailable, restrict printer driver access to trusted users and monitor for suspicious driver-related activity.

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
Color Laser 150 4zb94aHardware / appliance
Affected:all versions
Color Laser 150 4zb95aHardware / appliance
Affected:all versions
Color Laser Mfp 170 4zb96aHardware / appliance
Affected:all versions
Color Laser Mfp 170 4zb97aHardware / appliance
Affected:all versions
Color Laser Mfp 170 6hu08aHardware / appliance
Affected:all versions
Color Laser Mfp 170 6hu09aHardware / appliance
Affected:all versions
Laser 100 209u7aHardware / appliance
Affected:all versions
Laser 100 4zb79aHardware / appliance
Affected:all versions

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. List installed printers to find affected models
    Open Windows Settings > Devices > Printers & scanners, or run 'Get-Printer | Select-Object Name' in PowerShell, and look for any of these model identifiers: HP Color Laser 150 (4zb94a, 4zb95a), HP Color Laser Mfp 170 (4zb96a, 4zb97a, 6hu08a, 6hu09a), HP Laser 100 (209u7a, 4zb79a)
    Affected if Any of the listed model numbers appear in the installed printers list
  2. Check printer driver version
    Right-click each affected printer in the Printers list, select Printer Properties, and examine the Driver version field. Alternatively, run 'Get-PrinterDriver -Name '*' | Select-Object Name,DriverVersion' in PowerShell to list all printer drivers and their versions
    Affected if A driver with version information shows the affected printer model installed; all versions of these specific models are vulnerable
  3. Verify print spooler service is running
    Open Services (services.msc) and locate the Print Spooler service, or run 'Get-Service Spooler' in PowerShell. The vulnerable driver loads into this Windows service
    Affected if Print Spooler is running with an affected printer driver loaded, enabling the vulnerability path
  4. Check for driver files in system directories
    Navigate to C:\Windows\System32\spool\drivers\x64\3 (or the equivalent folder for your architecture) and look for driver files (such as .dll, .drv, or .sys files) associated with the affected HP printer models
    Affected if Driver files for any of the affected model numbers (4zb94a, 4zb95a, 4zb96a, 4zb97a, 6hu08a, 6hu09a, 209u7a, 4zb79a) are present in the driver directory

You are affected if any of the eight specific HP printer model numbers listed (4zb94a, 4zb95a, 4zb96a, 4zb97a, 6hu08a, 6hu09a, 209u7a, 4zb79a) appear in your Windows installed printers or driver files, as all versions of these models contain the vulnerable driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available driver updates from HP or Samsung for affected LaserJet and Samsung printer models. If updates are unavailable, restrict printer driver access to trusted users and monitor for suspicious driver-related activity.

Fix this in Color Laser 150 4zb94a Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3438 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-3438 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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