CVE-2017-14349
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 · uneditedAn authentication vulnerability in HPE SiteScope product versions 11.2x and 11.3x, allows read-only accounts to view all SiteScope interfaces and monitors, potentially exposing sensitive data.
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 confidenceHPE SiteScope versions 11.2x and 11.3x contain an authentication flaw where read-only accounts can bypass intended access restrictions and view all SiteScope interfaces and monitors, potentially exposing sensitive monitoring data and system configurations.
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= 11.20= 11.21= 11.22= 11.23= 11.24= 11.24.391= 11.30= 11.30.521= 11.31= 11.32= 11.33CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify installed HPE SiteScope versionLocate the SiteScope installation directory and check the version file or use the SiteScope administration interface version information panel. Common locations include the main SiteScope directory or the help/about section of the web interface.Affected if The installed version matches any of the following: 11.20, 11.21, 11.22, 11.23, 11.24, 11.24.391, 11.30, 11.30.521, 11.31, 11.32, or 11.33.
-
Confirm read-only user accounts existAccess the SiteScope user management interface and enumerate accounts. Look for accounts with read-only or viewer-level permissions assigned in the user or group configuration settings.Affected if One or more read-only or viewer-type accounts are configured in the SiteScope user database.
-
Verify authentication bypass conditionLog in using a read-only account and attempt to access interfaces, monitors, or configuration data that should be restricted to administrative or privileged users. Compare the accessible content against what the account permissions should allow.Affected if A read-only account can view content, interfaces, or monitors that should be restricted to higher-privilege users, indicating the authentication bypass is present.
-
Check for sensitive data exposureWith the read-only account, navigate through all available SiteScope sections including monitor configurations, alerts, templates, and system settings to identify if sensitive information is accessible beyond the intended scope.Affected if The read-only account can view monitoring data, system configurations, or other sensitive information that should not be visible to users with read-only privileges.
A user is affected if HPE SiteScope version 11.20 through 11.33 is installed AND read-only accounts exist that can bypass access restrictions to view restricted interfaces or sensitive monitoring data.
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 HPE SiteScope to a patched version and review all read-only account permissions to ensure proper access controls are enforced.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14349 — 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-14349 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