Futuresmart 4Operating system · Hp

CVE-2024-0407

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-21

Fix available

A fix is available. Upgrade to 2309110_002016 / 2309110_002022 or later.

See remediation →

74/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Certain HP Enterprise LaserJet, and HP LaserJet Managed Printers are potentially vulnerable to information disclosure, when connections made by the device back to services enabled by some solutions may have been trusted without the appropriate CA certificate in the device's certificate store.

Technical summary

dbcve analysis · moderate confidence

HP Enterprise LaserJet and HP LaserJet Managed Printers trust outbound connections to certain solution services without proper CA certificate validation, allowing potential man-in-the-middle attacks that could disclose sensitive information transmitted by the device.

MitigationApply HP firmware updates when available and ensure proper CA certificates are installed in the device certificate store for all outbound service connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Futuresmart 4Operating system

Affected:< 2411265_067635< 2411265_067634< 2411265_067627< 2411265_067630< 2411265_067628< 2411265_067632all versions

Futuresmart 3Operating system

Affected:< 2309110_002023< 2309110_002029< 2309110_002016< 2309110_002022< 2309110_002028

Futuresmart 5Operating system

Affected:< 2507252_046145< 2507252_046159< 2507252_046129< 2507252_046112< 2507252_046140< 2507252_046117< 2507252_046111< 2507252_046144< 2507252_046153< 2507252_046166< 2507252_046130< 2507252_046160

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Am I affected?

dbcve checks

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

Identify printer model and Futuresmart version

Access the printer's embedded web server (EWS) by entering the printer's IP address in a web browser. Navigate to the 'General' or 'Information' tab to find the product name and the Futuresmart firmware version (usually labeled as 'FutureSmart version' or similar).

Affected if The printer is an HP Enterprise LaserJet or HP LaserJet Managed model running Futuresmart version 3, 4, or 5.
Check installed firmware version for Futuresmart 4

In the EWS, locate the firmware version number (typically shown as a build number like '2411265_XXXXXX' under 'Device Information' or 'General' > 'Information'). Compare this version against the affected thresholds: < 2411265_067635, < 2411265_067634, < 2411265_067627, < 2411265_067630, < 2411265_067628, < 2411265_067632.

Affected if The installed Futuresmart 4 firmware version is lower than any of the listed thresholds, or if the version shows only a base number with no specific build suffix.
Check installed firmware version for Futuresmart 3

In the EWS under 'Device Information', find the firmware build number (format like '2309110_XXXXXX'). Compare against the affected thresholds: < 2309110_002023, < 2309110_002029, < 2309110_002016, < 2309110_002022, < 2309110_002028.

Affected if The installed Futuresmart 3 firmware version is lower than any of the listed thresholds.
Check installed firmware version for Futuresmart 5

In the EWS under 'Device Information' or ' firmware Information', locate the firmware build number (format like '2507252_XXXXXX'). Compare against all affected thresholds: < 2507252_046145, < 2507252_046159, < 2507252_046129, < 2507252_046112, < 2507252_046140, < 2507252_046117, < 2507252_046111, < 2507252_046144, < 2507252_046153, < 2507252_046166, < 2507252_046130, < 2507252_046160.

Affected if The installed Futuresmart 5 firmware version is lower than any of the listed thresholds.

The environment is affected if the printer runs an HP Enterprise LaserJet or HP LaserJet Managed model with Futuresmart 3, 4, or 5 firmware version below the thresholds listed for the respective Futuresmart version.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2309110_002016 / 2309110_002022 / 2309110_002023 or later

Fixed in 2309110_0020162309110_0020222309110_002023

Interim mitigation

Apply HP firmware updates when available and ensure proper CA certificates are installed in the device certificate store for all outbound service connections.

Recommended fix Moderate confidence

Latest Futuresmart firmware for your printer model (Futuresmart 4 ≥ 2411265_067635, Futuresmart 3 ≥ 2309110_002023, Futuresmart 5 ≥ 2507252_046145)

1. Identify the current Futuresmart firmware version installed on the HP LaserJet printer by accessing the printer's embedded web server (EWS) or control panel
2. Navigate to the HP support website (support.hp.com) and locate the firmware download section for your specific HP LaserJet printer model
3. Download the latest available Futuresmart firmware for your model
4. Access the printer's EWS, go to the 'General' or ' firmware' settings section
5. Upload and install the new firmware file, following the on-screen prompts
6. After installation, verify the new firmware version matches or exceeds the fixed version thresholds: Futuresmart 4 ≥ 2411265_067635, Futuresmart 3 ≥ 2309110_002023, Futuresmart 5 ≥ 2507252_046145
7. Restart the printer to ensure the firmware update is fully applied

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

Fix this in Futuresmart 4 Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

11.0 hours of engineering $1,980

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-0407 — 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

Primary sources

support.hp.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-0407?

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.

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

At a glance

A fix existsUpgrade to 2309110_002016 / 2309110_002022 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Futuresmart 4

Remediation

Need this fixed?

Fix this in Futuresmart 4 11 hrs · Moderate

Typical engagement from $1,980

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-0407 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References