CVE-2017-12547
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 local arbitrary command execution vulnerability in HPE System Management Homepage for Windows and Linux version prior to v7.6.1 was found.
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 confidenceThis is a local privilege escalation/arbitrary command execution vulnerability in HPE System Management Homepage (SMH) versions prior to v7.6.1 on Windows and Linux. An authenticated local attacker with access to the system could execute arbitrary commands with elevated privileges through the SMH interface.
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< 7.6.1CVSS 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
- High
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:N/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.
-
Confirm HPE SMH is installedCheck your system for HPE System Management Homepage software using system inventory tools, installed programs list, or package managers on LinuxAffected if SMH is not found on the system, the vulnerability does not apply
-
Determine installed SMH versionUse system tools to query the installed version of HPE System Management Homepage (such as 'rpm -q' on Linux or Add/Remove Programs on Windows)Affected if Unable to determine the version, assume potentially affected
-
Compare version against the thresholdCheck if the installed version is below 7.6.1Affected if Installed version is lower than 7.6.1, the system is vulnerable
-
Verify SMH service accessibilityDetermine if the SMH web interface is running and accessible on ports 2301 or 2381 (default SMH ports)Affected if Service is exposed but version is below 7.6.1, the attack surface is present
-
Assess local access controlsReview which users have authenticated access to the system hosting SMHAffected if Untrusted local users have accounts on this server, they could potentially exploit this flaw
You are affected if HPE System Management Homepage is installed with a version lower than 7.6.1 and untrusted local users have access to 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 data7.6.1
Upgrade HPE System Management Homepage to version 7.6.1 or later to remediate this vulnerability. If immediate patching is not possible, restrict physical and logical access to the server hosting SMH.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12547 — 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-2017-12547 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