dbcve.org
Futuresmart 3Operating system · Hp

CVE-2019-6334

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to 2309021_581886 / 2309021_581889 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
HP LaserJet, PageWide, OfficeJet Enterprise, and LaserJet Managed Printers have a solution to check application signature that may allow potential execution of arbitrary code.

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

This vulnerability in HP LaserJet, PageWide, OfficeJet Enterprise, and LaserJet Managed Printers involves a flaw in the application signature verification mechanism that can be bypassed, allowing an attacker to execute arbitrary code on affected devices. The signature check intended to validate firmware/applications is insufficient, enabling malicious code injection.

MitigationApply available firmware updates from HP for all affected printer models. Until patches are available, restrict network access to printers and disable unnecessary services.

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
Futuresmart 3Operating system
Affected:< 2309021_581893< 2309021_581898< 2309021_581886< 2309021_581895< 2309021_581902< 2309021_581899< 2309021_581889< 2309021_581900< 2309021_581892< 2309021_581909< 2309021_581910< 2309021_581897
Futuresmart 4Operating system
Affected:< 2408067_049135< 2408067_049141< 2408067_049131< 2408067_049158< 2408067_049164< 2408067_049127< 2408071_000209< 2408067_049134< 2408071_000205< 2408071_000142< 2408071_000121< 2408071_000187

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
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 checks

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

  1. Identify printer model and firmware version
    Access the printer's embedded web server (EWS) by entering the printer's IP address in a browser. Navigate to the 'General' or 'Information' tab to view the device name and firmware version. Alternatively, check via the printer control panel under 'Setup' > 'Service' > 'Report' or print a configuration page.
    Affected if The firmware version displayed matches a Futuresmart 3 or Futuresmart 4 version that falls below the listed thresholds.
  2. Verify Futuresmart 3 version
    If the firmware version starts with '2309021_', compare the full version number against the affected list: 581893, 581898, 581886, 581895, 581902, 581899, 581889, 581900, 581892, 581909, 581910, 581897. Any version lower than these specific numbers is affected.
    Affected if The installed Futuresmart 3 firmware version is lower than any of the patched versions listed.
  3. Verify Futuresmart 4 version
    If the firmware version starts with '2408067_' or '2408071_', compare against the affected list. For 2408067_ versions: check against 049135, 049141, 049131, 049158, 049164, 049127, 049134. For 2408071_ versions: check against 000209, 000205, 000142, 000121, 000187.
    Affected if The installed Futuresmart 4 firmware version is lower than any of the patched versions listed for its branch.
  4. Confirm signature verification is in use
    The vulnerability specifically affects the application signature verification mechanism. This is a built-in security feature that validates firmware and application packages. There is no separate configuration to disable; the flaw exists in how the device validates signatures regardless of whether the feature is enabled by default.
    Affected if The device runs any affected Futuresmart 3 or 4 firmware version, meaning the vulnerable signature verification code is present.

A user is affected if their HP LaserJet, PageWide, OfficeJet Enterprise, or LaserJet Managed Printer runs Futuresmart firmware version 3 below 2309021_581xxx or Futuresmart 4 below 2408067_049xxx/2408071_000xxx thresholds.

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.

dbcve · scoped
Upgrade available Upgrade to 2309021_581886 / 2309021_581889 / 2309021_581892 or later
Fixed in 2309021_5818862309021_5818892309021_581892
Interim mitigation

Apply available firmware updates from HP for all affected printer models. Until patches are available, restrict network access to printers and disable unnecessary services.

Recommended fix Moderate confidence

Upgrade to Futuresmart 3 firmware version 2309021_581893 or higher, or Futuresmart 4 firmware version 2408067_049135 or higher (specific version depends on exact printer model)

  1. 1. Identify the current Futuresmart firmware version on the affected HP printer by printing a configuration page or accessing the embedded web server
  2. 2. Navigate to the HP support website (support.hp.com) and locate the firmware update for your specific printer model
  3. 3. Download the appropriate Futuresmart 3 or Futuresmart 4 firmware version based on your device: for Futuresmart 3, download version 2309021_581893 or higher (or 581898, 581886, 581895 depending on your specific model); for Futuresmart 4, download version 2408067_049135 or higher (or 049141, 049131, 049158 depending on your specific model)
  4. 4. Access the printer's embedded web server (EWS) via HTTP/HTTPS
  5. 5. Navigate to the Firmware Update or General Settings section
  6. 6. Upload the downloaded firmware file and initiate the update process
  7. 7. Wait for the firmware update to complete and verify the printer reboots successfully
  8. 8. After reboot, confirm the new firmware version is installed and test printer functionality
Caveat Firmware updates may temporarily interrupt printer availability; ensure print jobs are paused and backup any critical configuration settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Futuresmart 3 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2019-6334 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