Support AssistantApplication · Hp

CVE-2025-43019

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 potential security vulnerability has been identified in the HP Support Assistant, which allows a local attacker to escalate privileges via an arbitrary file deletion.

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 contains a local privilege escalation vulnerability where an attacker with low-privilege access can delete arbitrary files, leading to privilege escalation. The arbitrary file deletion likely enables deletion of security-related files or exploitation of file-overwrite conditions to gain elevated (SYSTEM) privileges.

MitigationApply vendor-supplied patches or updates for HP Support Assistant as they become available. Until a patch is released, restrict local non-privileged user access to the HP Support Assistant installation directories and monitor for suspicious file deletion activities.

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
Support AssistantApplication
Affected:= 9.46.17.0

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

CVSS:3.1/AV:L/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. Verify HP Support Assistant is installed
    Look for HP Support Assistant in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check for the installation directory typically at C:\Program Files\HP\HP Support Assistant or C:\Program Files (x86)\HP\HP Support Assistant
    Affected if HP Support Assistant is present on the system
  2. Determine installed version
    Right-click on HP Support Assistant.exe in the installation folder, select Properties, and view the File Version on the Details tab. Alternatively, run 'wmic product get name,version' or check the Uninstall registry key for the version value.
    Affected if The version displayed is exactly 9.46.17.0
  3. Check file deletion permissions for low-privilege users
    Right-click the HP Support Assistant installation folder, go to Properties > Security, and review the permissions for Users or non-privileged groups. Verify if the Write or Delete permission is granted.
    Affected if Users or low-privilege groups have Delete permissions on the installation directory or its subdirectories
  4. Inspect for security-related file removal
    Check if security-critical files such as .dll files in the HP Support Assistant folder, Windows Defender definitions, or other security software files have been deleted or can be deleted by a standard user account.
    Affected if A standard user can delete files in the HP Support Assistant directory or related security files

The system is affected only if HP Support Assistant version 9.46.17.0 is installed AND low-privilege users have file deletion permissions on the application 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for HP Support Assistant as they become available. Until a patch is released, restrict local non-privileged user access to the HP Support Assistant installation directories and monitor for suspicious file deletion activities.

Fix this in Support Assistant Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-43019 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