CVE-2019-6328
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 · uneditedHP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6329.
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 confidenceHP Support Assistant versions 8.7.50 and earlier contain a local privilege escalation vulnerability that allows an authenticated local user to gain SYSTEM-level privileges and perform unauthorized modifications to directories or files on the affected system. This likely stems from improper privilege validation or insecure file/directory permission handling within the application.
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<= 8.7.50CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify HP Support Assistant is installedCheck for the presence of HP Support Assistant on the system. On Windows, look in Program Files or Program Files (x86) for an HP Support Assistant folder, or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'HP Support Assistant'.Affected if The application is found on the system and no further version check has been performed.
-
Determine installed versionLocate the version information for HP Support Assistant. In Windows, right-click the desktop shortcut or the executable (typically in C:\Program Files\HP\HP Support Assistant\bin\HPSupportAssistant.exe) and view Properties > Details, or open the application and navigate to Help > About. Compare the version number to 8.7.50.Affected if The installed version is 8.7.50 or any earlier version.
-
Inspect HP Support Assistant directory permissionsRight-click the HP Support Assistant installation directory (commonly C:\Program Files\HP\HP Support Assistant), select Properties > Security, and examine the permissions for standard user accounts. Verify whether non-admin users have Write or Modify permissions on system directories or configuration folders used by the application.Affected if Standard user accounts have Write, Modify, or Full Control permissions on application directories or config files.
-
Check for unauthorized system modificationsReview system directories or critical files that HP Support Assistant accesses for unexpected changes. Use Windows Event Viewer or compare file integrity baselines to identify modifications performed by the application or its updater component.Affected if System directories, files, or registry keys show modifications that were not performed by an administrator or that occurred during HP Support Assistant execution.
A system is affected if HP Support Assistant version 8.7.50 or earlier is installed AND standard user accounts have elevated permissions or unauthorized system modifications are present.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade HP Support Assistant to a version newer than 8.7.50. Organizations should deploy the updated version enterprise-wide and verify that standard user accounts cannot modify system directories or files post-update.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6328 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6328 in production — separate from our analysis above.
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.
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.
- 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