Ucmdb Configuration ManagerApplication · Hp

CVE-2017-14352

MEDIUM · 6.1 CVSS v3.0 Published 2017-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A potential security vulnerability has been identified in HP UCMDB Configuration Manager versions 10.10, 10.11, 10.20, 10.21, 10.22, 10.23. These vulnerabilities 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in HP UCMDB Configuration Manager versions 10.10 through 10.23 that can be remotely exploited, allowing attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpgrade to a patched version of HP UCMDB Configuration Manager or apply vendor-supplied security patches to remediate the XSS vulnerability.

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
Ucmdb Configuration ManagerApplication
Affected:= 10.10= 10.11= 10.20= 10.21= 10.22= 10.23

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm HP UCMDB Configuration Manager is installed
    Check your systems for the presence of HP UCMDB Configuration Manager software. Common installation paths include C:\Program Files\HP\UCMDB\ or /opt/HP/UCMDB/ on Linux systems.
    Affected if The product is not installed in your environment
  2. Identify the installed version
    Locate the version information for your HP UCMDB installation. This is typically found in the product UI under Help > About, in the installation directory readme files, or via the web management interface.
    Affected if Unable to determine version information from your installation
  3. Compare against affected versions
    Check if your installed version matches any of these: 10.10, 10.11, 10.20, 10.21, 10.22, or 10.23
    Affected if Your version matches one of the listed affected versions
  4. Verify web interface accessibility
    Determine if the HP UCMDB web management portal is accessible on your network. The XSS vulnerability is exploitable through the web interface.
    Affected if The web interface is exposed and your version is in the affected list

You are affected if HP UCMDB Configuration Manager version 10.10, 10.11, 10.20, 10.21, 10.22, or 10.23 is installed and the web management interface is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of HP UCMDB Configuration Manager or apply vendor-supplied security patches to remediate the XSS vulnerability.

Fix this in Ucmdb Configuration Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14352 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14352 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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