dbcve.org
26k70b FirmwareOperating system · Hp

CVE-2024-2209

MEDIUM · 6.3 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 2349c / 2349d or later.
See remediation →
65/100
Remediation priority · Elevated
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 user with administrative privileges can create a compromised dll file of the same name as the original dll within the HP printer’s Firmware Update Utility (FUU) bundle and place it in the Microsoft Windows default downloads directory which can lead to potential arbitrary code execution.

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 · high confidence

This is a DLL search order hijacking vulnerability in HP's Firmware Update Utility (FUU). An attacker with administrative privileges can place a malicious DLL with the same name as a legitimate DLL in the Windows default downloads directory. When FUU runs, it loads the DLL from the downloads directory instead of its own secure application directory, leading to arbitrary code execution with the privileges of the FUU process.

MitigationHP should release an updated FUU that uses secure DLL loading practices (specifying full paths, using SetDllDirectory, or manifest-based binding). Organizations should scan download directories for suspicious DLLs and implement application whitelisting to prevent unauthorized DLL execution.

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
26k70b FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
297x1a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
2a9q5a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
26k72a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
26k69a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
26k70a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
26k71a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d
26k68a FirmwareOperating system
Affected:< 2349b< 2349c< 2349d

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

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

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. Verify HP Firmware Update Utility (FUU) is installed
    Check for FUU installation by looking in Program Files for HP folders, or run 'Get-Process' to check for FUU-related processes, or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for HP Firmware Update entries
    Affected if HP FUU software is present on the system and the associated firmware versions are below 2349b/2349c/2349d
  2. Identify firmware versions of HP devices
    Use FUU to query connected HP device firmware versions, or run HP firmware diagnostic tools to list installed firmware versions for the affected model numbers (26k70b, 297x1a, 2a9q5a, 26k72a, 26k69a, 26k70a, 26k71a, 26k68a)
    Affected if Any HP device firmware version is less than 2349b, 2349c, or 2349d for the listed model numbers
  3. Inspect Windows downloads directory for suspicious DLLs
    List all .dll files in the user's default downloads directory (typically %USERPROFILE%\Downloads) and check for unexpectedly placed DLLs with common Windows names (such as ws2_32.dll, version.dll, or other system DLLs) that were not intentionally downloaded
    Affected if Unexpected DLL files exist in the downloads directory, especially DLLs with names matching system libraries that could be exploited via search order hijacking
  4. Review FUU execution logs for DLL load events
    Check FUU logs (typically found in %APPDATA%\HP or %PROGRAMDATA%\HP\FUU\Logs) for DLL loading activities, particularly any DLLs loaded from the downloads directory path
    Affected if FUU logs show DLLs being loaded from paths outside the FUU application directory, especially from user directories

You are affected if HP Firmware Update Utility is installed and the firmware version of any HP device (26k70b, 297x1a, 2a9q5a, 26k72a, 26k69a, 26k70a, 26k71a, 26k68a) is below 2349b/2349c/2349d, or if suspicious DLLs are present in the downloads directory.

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 2349c / 2349d / 2349b or later
Fixed in 2349c2349d2349b
Interim mitigation

HP should release an updated FUU that uses secure DLL loading practices (specifying full paths, using SetDllDirectory, or manifest-based binding). Organizations should scan download directories for suspicious DLLs and implement application whitelisting to prevent unauthorized DLL execution.

Recommended fix Moderate confidence

HP Printer Firmware version 2349b/2349c/2349d or later (depending on your specific model branch)

  1. Identify your exact HP printer model number from the device display or product label
  2. Navigate to HP Support (support.hp.com) and enter your printer model to access the drivers and firmware section
  3. Locate the firmware update utility (FUU) for your specific printer model
  4. Download the latest firmware version (look for version 2349b, 2349c, 2349d or later)
  5. Ensure you have administrative privileges on the Windows machine
  6. Run the downloaded FUU installer and follow the on-screen instructions to update the printer firmware
  7. After the update completes, verify the firmware version has been updated to 2349b or higher, 2349c or higher, or 2349d or higher
Caveat Firmware updates may reset some printer settings to defaults; reconfigure network settings, custom paper sizes, and other preferences after upgrading

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

Fix this in 26k70b Firmware 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 the upgrade done

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-2024-2209 — 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-2024-2209 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