dbcve.org
Urbancode DeployApplication · Ibm

CVE-2016-9006

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

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
IBM UrbanCode Deploy 6.1 and 6.2 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM Reference #: C1000264.

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 confidence

IBM UrbanCode Deploy 6.1 and 6.2 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed malicious JavaScript code into the interface, which executes in the browsers of other users viewing the infected content, potentially allowing session hijacking and credentials theft within trusted sessions.

MitigationApply IBM's patch C1000264 or upgrade to UrbanCode Deploy 6.2.1 or later as specified in the IBM reference. Alternatively, implement robust input validation and output encoding as a compensating control until the patch can be deployed.

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
Urbancode DeployApplication
Affected:= 6.1= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.1= 6.1.1.1= 6.1.1.2= 6.1.1.3= 6.1.1.4= 6.1.1.5= 6.1.1.6

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Identify the installed version of IBM UrbanCode Deploy
    Locate the version information in the product's About section, typically accessible via the Web UI help menu, or check the installation directory for a version manifest file. In the data directory, the version may be recorded in a properties file or manifest.
    Affected if The installed version matches any of the following: 6.1, 6.1.0.1, 6.1.0.2, 6.1.0.3, 6.1.0.4, 6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.3, 6.1.1.4, 6.1.1.5, or 6.1.1.6
  2. Confirm the Web UI component is enabled and accessible
    Verify that the Web UI service is running and reachable by attempting to access the UrbanCode Deploy web interface via its configured URL and port.
    Affected if The Web UI is accessible and the application version falls within the affected range listed above
  3. Review application logs for indicators of XSS exploitation attempts
    Examine the IBM UrbanCode Deploy server logs, particularly the Web UI logs and application logs found in the installation logs directory, for unusual script tags or JavaScript patterns in user-supplied content.
    Affected if Logs contain unexpected script tags, JavaScript function calls, or HTML markup in fields that should contain plain text only
  4. Inspect stored user content and configuration fields for malicious scripts
    Review stored application data such as component names, process step descriptions, resource properties, and other user-editable text fields in the database or through the UI for any injected script tags or JavaScript code.
    Affected if Any stored fields contain script tags, event handler attributes, or JavaScript code that was not entered by an authorized administrator

A user is affected if their IBM UrbanCode Deploy installation version is 6.1 through 6.1.1.6 and the Web UI is enabled, with the risk increasing if suspicious script content is found in stored application fields.

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

Apply IBM's patch C1000264 or upgrade to UrbanCode Deploy 6.2.1 or later as specified in the IBM reference. Alternatively, implement robust input validation and output encoding as a compensating control until the patch can be deployed.

Fix this in Urbancode Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-9006 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