CVE-2017-14354
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 remote cross-site scripting vulnerability in HP UCMDB Foundation Software versions 10.10, 10.11, 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, and 10.33 could be remotely exploited to allow cross-site scripting.
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 remote cross-site scripting (XSS) vulnerability in HP UCMDB Foundation Software versions 10.10-10.33 allows attackers to inject malicious scripts through unsanitized user input, potentially stealing session cookies or performing actions on behalf of authenticated users.
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= 10.10= 10.11= 10.20= 10.21= 10.22= 10.30= 10.31= 10.32= 10.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 if HP UCMDB Foundation Software is deployedCheck for running processes named 'ucmdb' or 'UCMDB' on servers, or look for HP UCMDB installation directories. Common paths may include C:\HP\UCMDB\ or /opt/HP/UCMDB/Affected if HP UCMDB Foundation Software is found running in the environment
-
Determine the installed version of HP UCMDBLocate the version file or check the product information. Common methods include: checking the 'version.properties' or 'build.info' files in the installation directory, or accessing the UCMDB web interface and looking at the About/Help sectionAffected if The installed version matches 10.10, 10.11, 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, or 10.33
-
Verify web interfaces are accessibleCheck if UCMDB web clients or REST/SOAP APIs are exposed. Common endpoints include /ucmdb-api, /ucmdb-ui, or the main UCMDB web login page. Test connectivity to typical ports such as 8080, 8443, or 443Affected if UCMDB web interfaces are accessible over the network, indicating the vulnerable XSS attack surface is exposed
-
Review user input handling in UCMDBIdentify which UCMDB web interfaces accept user input (search fields, parameter inputs, form submissions). These are the potential injection points for the XSS vulnerabilityAffected if Any web-accessible UCMDB interface accepts unsanitized user input and falls within the affected version range
You are affected if HP UCMDB Foundation Software versions 10.10 through 10.33 are installed and web interfaces accepting user input are accessible.
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 dataApply vendor-supplied patches for affected versions. As a temporary measure, implement input validation and output encoding on user-supplied data, and consider deploying a WAF rule to block XSS attack patterns.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14354 — 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-14354 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