CVE-2019-11987
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 security vulnerability in HPE Smart Update Manager (SUM) prior to v8.4 could allow local unauthorized elevation of privilege.
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 confidenceHPE Smart Update Manager versions prior to 8.4 contain a local privilege escalation vulnerability allowing an unauthorized attacker to gain elevated system privileges on the host where SUM is installed. The vulnerability is exploitable locally, requiring the attacker to have some level of access to the target system.
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.4CVSS 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.
-
Locate HPE Smart Update Manager installationCheck common installation paths such as C:\Program Files\HPE\SUM or /opt/hp/sum, and look for SUM executable files (suminfo.exe, SUM.exe, or sum binary)Affected if SUM is found installed on the system
-
Identify installed SUM versionRun the SUM version command: suminfo.exe -v (Windows) or ./suminfo -v (Linux). Alternatively, check Add/Remove Programs on Windows or rpm query on Linux for the package versionAffected if Version returned is lower than 8.4 or the version cannot be determined
-
Check SUM service statusOn Windows, run services.msc and look for 'HPE Smart Update Manager' service. On Linux, run 'systemctl status hpsum' or 'service hpsum status'Affected if SUM service is installed and running on the host
-
Verify current user privilegesRun 'whoami /all' (Windows) or 'id' (Linux) to determine if the current user is in the Administrators group or has sudo privilegesAffected if Current user has limited privileges and SUM is installed with elevated service account configuration
If HPE Smart Update Manager is installed and the version is below 8.4, the system is vulnerable to local privilege escalation via this CVE.
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 data8.4
Upgrade HPE Smart Update Manager to version 8.4 or later to remediate this vulnerability. Verify the upgrade in a test environment before production deployment.
- 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-11987 — 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-11987 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