CVE-2019-6333
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 · uneditedA potential security vulnerability has been identified with certain versions of HP Touchpoint Analytics prior to version 4.1.4.2827. This vulnerability may allow a local attacker with administrative privileges to execute arbitrary code via an HP Touchpoint Analytics system service.
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 confidenceA local privilege escalation vulnerability in HP Touchpoint Analytics system service versions prior to 4.1.4.2827 allows an attacker with existing administrative privileges to execute arbitrary code through the HP Touchpoint Analytics service.
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< 4.1.4.2827CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Check if HP Touchpoint Analytics service existsOpen Services console (services.msc) and look for 'HP Touchpoint Analytics Service' or run 'Get-Service -Name *Touchpoint*' in PowerShellAffected if The service is not found, meaning the product is not installed and the system is not affected
-
Identify the installed version of HP Touchpoint AnalyticsCheck the file version of 'C:\Program Files\HP\HP Touchpoint Analytics Service\HP.TouchpointAnalytics.Service.exe' by right-clicking the file, selecting Properties, and viewing the Details tab, or use PowerShell: (Get-Item 'C:\Program Files\HP\HP Touchpoint Analytics Service\HP.TouchpointAnalytics.Service.exe').VersionInfo.FileVersionAffected if The version displayed is lower than 4.1.4.2827 (for example, 4.1.4.2826 or earlier)
-
Confirm the service is runningIn Services console, verify the HP Touchpoint Analytics Service status is 'Running', or run 'Get-Service -Name *Touchpoint* | Select-Object Status'Affected if The service is running and the version is below 4.1.4.2827
-
Verify current user has administrative privilegesRun 'whoami /groups' and look for 'BUILTIN\Administrators' or run '[Security.Principal.WindowsPrincipal]::new([Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)' in PowerShell which returns True if adminAffected if The current user has administrator privileges and the service version is below 4.1.4.2827
You are affected if HP Touchpoint Analytics is installed with a version lower than 4.1.4.2827, the service is running, and you have administrative privileges on the system.
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 data4.1.4.2827
Update HP Touchpoint Analytics to version 4.1.4.2827 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6333 — 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-6333 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