dbcve.org
Hp Device ManagerApplication · Hp

CVE-2023-26297

HIGH · 8.8 CVSS v3.1 Published 2023-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Previous versions of HP Device Manager (prior to HPDM 5.0.10) could potentially allow command injection and/or elevation of privileges.

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

HP Device Manager versions prior to 5.0.10 contain a vulnerability that allows command injection and/or privilege escalation. The specific attack vector and injection point are not detailed in the available description, but the vulnerability is exploitable locally or remotely (CVSS 8.8 indicates high severity with network-accessible attack surface).

MitigationUpgrade HP Device Manager to version 5.0.10 or later to address this vulnerability. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious command 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
Hp Device ManagerApplication
Affected:= 5.0= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.7.1= 5.0.8= 5.0.9

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

CVSS:3.1/AV:N/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. Confirm HP Device Manager installation
    Check for HP Device Manager in installed programs. On Windows, review the Programs and Features list or check for the installation directory (commonly under C:\Program Files\HP\HP Device Manager or C:\Program Files (x86)\HP\HP Device Manager). Also check for the HP Device Manager service using 'services.msc' or the command 'sc query type= service state= all | findstr /i "HP Device"'.
    Affected if HP Device Manager is present on the system.
  2. Identify installed version
    Locate the version information. Check the executable properties of 'HpDeviceManager.exe' (typically in the installation bin folder), check the Windows registry under HKLM\SOFTWARE\Hewlett-Packard\HP Device Manager\CurrentVersion, or review the uninstall entry in the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} for the DisplayVersion value.
    Affected if The version returned is 5.0, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.7.1, 5.0.8, or 5.0.9.
  3. Check if management interface is network-accessible
    HP Device Manager typically exposes a management service on TCP port 2375 (or 2376 for SSL). Use 'netstat -an | findstr "2375\|2376"' to check if the service is listening on external interfaces. Also verify firewall rules allowing inbound connections to these ports from untrusted networks.
    Affected if The HP Device Manager service is bound to 0.0.0.0 or an external IP address and accepting connections on ports 2375/2376.
  4. Review service configuration and privileges
    Examine the HP Device Manager service account using 'sc qc "HP Device Manager"' (or the exact service name) to identify the logon account. Check if the service runs with elevated privileges such as LocalSystem or a domain administrator account.
    Affected if The service runs with high-privilege account (LocalSystem, administrator, or domain admin) and is network-accessible.

If HP Device Manager is installed and the version is 5.0 through 5.0.9 (excluding 5.0.10), the system is affected by this vulnerability, especially if the management interface is exposed on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HP Device Manager to version 5.0.10 or later to address this vulnerability. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious command execution.

Recommended fix High confidence

HP Device Manager 5.0.10

  1. 1. Download HP Device Manager version 5.0.10 from the official HP support website (support.hp.com)
  2. 2. Review HP's release notes for HPDM 5.0.10 to understand any changes or requirements
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Back up the current HP Device Manager configuration and database
  5. 5. Stop the HP Device Manager service
  6. 6. Install HP Device Manager version 5.0.10
  7. 7. Start the HP Device Manager service
  8. 8. Verify the installation and test functionality

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

Fix this in Hp Device Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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