dbcve.org
FusionApplication · Hp

CVE-2022-38395

HIGH · 7.8 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 1.38.2601.0 / 9.11 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Support Assistant uses HP Performance Tune-up as a diagnostic tool. HP Support Assistant uses Fusion to launch HP Performance Tune-up. It is possible for an attacker to exploit the DLL hijacking vulnerability and elevate privileges when Fusion launches the HP Performance Tune-up.

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 Support Assistant launches HP Performance Tune-up through Fusion, which is vulnerable to DLL hijacking. An attacker can place a malicious DLL in the search path that Fusion uses when loading HP Performance Tune-up, allowing execution with elevated privileges.

MitigationApply the vendor patch from HP for HP Support Assistant, or temporarily disable/uninstall the HP Performance Tune-up and Fusion components until the patch can be applied.

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
FusionApplication
Affected:< 1.38.2601.0
Support AssistantApplication
Affected:< 9.11

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check HP Support Assistant version
    Open Programs and Features (appwiz.cpl) or check the version in the HP Support Assistant installation directory (typically C:\Program Files\HP\Support Assistant\). Compare the installed version to the affected range: versions prior to 9.11 are vulnerable.
    Affected if HP Support Assistant version is installed and it is lower than 9.11
  2. Check HP Fusion component version
    Locate the Fusion component installation (typically in C:\Program Files\HP\Fusion\ or within the HP Support Assistant directory). Check the file version of the Fusion executable or DLL files. Compare to the affected version: versions prior to 1.38.2601.0 are vulnerable.
    Affected if HP Fusion is installed with a version lower than 1.38.2601.0
  3. Verify HP Performance Tune-up component exists
    Check for the presence of HP Performance Tune-up files on the system (typically in C:\Program Files\HP\Performance Tune-up\ or within the HP Support Assistant installation directory). This component is launched through Fusion and is the target of the DLL hijacking.
    Affected if HP Performance Tune-up component is installed on the system
  4. Confirm Fusion is configured to launch Performance Tune-up
    Examine the Fusion configuration or examine how HP Performance Tune-up is launched. Check if Fusion handles the invocation of HP Performance Tune-up - the vulnerability exploits the DLL search path when Fusion loads the Performance Tune-up functionality.
    Affected if Fusion is configured to launch or integrate with HP Performance Tune-up

A user is affected if HP Support Assistant version is below 9.11 AND HP Fusion version is below 1.38.2601.0 AND the HP Performance Tune-up component is present on the system, allowing DLL hijacking during the Fusion launch process.

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 1.38.2601.0 / 9.11 or later
Fixed in 1.38.2601.09.11
Interim mitigation

Apply the vendor patch from HP for HP Support Assistant, or temporarily disable/uninstall the HP Performance Tune-up and Fusion components until the patch can be applied.

Recommended fix High confidence

Fusion: 1.38.2601.0 or later | Support Assistant: 9.11 or later

  1. Identify current versions of HP Fusion and HP Support Assistant installed on the system
  2. Navigate to HP Support website (support.hp.com) and search for HP Support Assistant
  3. Download HP Support Assistant version 9.11 or later
  4. Install HP Support Assistant (this will also update the bundled Fusion component)
  5. Alternatively, if using HP Support Assistant, use the built-in update mechanism to check for and apply updates
  6. Verify that Fusion version is 1.38.2601.0 or later and Support Assistant version is 9.11 or later after installation

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

Fix this in Fusion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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