dbcve.org
Devops DeployApplication · Ibm

CVE-2024-22359

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 7.0.5.21 / 7.1.2.17 or later.
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
IBM UrbanCode Deploy (UCD) 7.0 through 7.0.5.20, 7.1 through 7.1.2.16, 7.2 through 7.2.3.9, 7.3 through 7.3.2.4 and IBM DevOps Deploy 8.0 through 8.0.0.1 are 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 X-Force ID: 280897.

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

Stored cross-site scripting (XSS) vulnerability in IBM UrbanCode Deploy and DevOps Deploy Web UI allows authenticated users to inject arbitrary JavaScript code that executes in other users' sessions within the trusted application context, potentially leading to session hijacking and credential disclosure.

MitigationApply IBM's security patches for this vulnerability by upgrading to fixed versions (UCD 7.0.5.21+, 7.1.2.17+, 7.2.3.10+, 7.3.2.5+, DevOps Deploy 8.0.0.2+) or later releases, and validate that the Web UI properly sanitizes user input.

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
Devops DeployApplication
Affected:>= 8.0.0.0, < 8.0.1.0
Urbancode DeployApplication
Affected:>= 7.0.0.0, < 7.0.5.21>= 7.1.0.0, < 7.1.2.17>= 7.2.0.0, < 7.2.3.10>= 7.3.0.0, < 7.3.2.5

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.1/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. Identify installed IBM UrbanCode Deploy or DevOps Deploy version
    Locate the version from the product's About page in the Web UI, or check the installation directory for a version file. On Linux/Unix, inspect /opt/ibm-ucd/server/etc/VERSION or similar installation artifacts. On Windows, check the installation folder properties or registry.
    Affected if The installed version falls within any of these ranges: DevOps Deploy 8.0.0.0 through before 8.0.1.0; UrbanCode Deploy 7.0.0.0 through before 7.0.5.21; 7.1.0.0 through before 7.1.2.17; 7.2.0.0 through before 7.2.3.10; or 7.3.0.0 through before 7.3.2.5
  2. Confirm Web UI is accessible
    Attempt to access the Web UI login page at the standard port (8080 or 8443) for your deployment. Verify the service is running by checking the process list or service status.
    Affected if The Web UI is exposed and accessible to users, which is required for the XSS to be exploitable
  3. Check for existing XSS payloads in application data
    Review application logs in the server logs directory for evidence of script injection attempts, or query the application's database for stored user-supplied content that may contain script tags. Look for patterns like <script>, javascript:, or event handlers in user profile fields, component names, or process variables.
    Affected if Malicious JavaScript code has been stored in the application database and could execute in other users' sessions
  4. Review recent user activity for suspicious input
    Audit user-created resources such as applications, components, environments, or processes for unusually encoded or embedded script content. Check user profile fields and any user-generated text areas.
    Affected if Users have injected script content that gets rendered without proper sanitization in the Web UI

You are affected if your installed version is within any of the affected ranges AND the Web UI is accessible, since the vulnerability requires an authenticated user session to inject the XSS payload that then executes in other users' trusted sessions.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0.5.21 / 7.1.2.17 / 7.2.3.10 or later
Fixed in 7.0.5.217.1.2.177.2.3.10
Interim mitigation

Apply IBM's security patches for this vulnerability by upgrading to fixed versions (UCD 7.0.5.21+, 7.1.2.17+, 7.2.3.10+, 7.3.2.5+, DevOps Deploy 8.0.0.2+) or later releases, and validate that the Web UI properly sanitizes user input.

Recommended fix High confidence

IBM DevOps Deploy 8.0.1.0+ or IBM UrbanCode Deploy 7.0.5.21+, 7.1.2.17+, 7.2.3.10+, or 7.3.2.5+ depending on your product line

  1. 1. Identify the currently installed IBM UrbanCode Deploy or IBM DevOps Deploy version and edition.
  2. 2. For IBM DevOps Deploy 8.0.x users: Plan upgrade to version 8.0.1.0 or later.
  3. 3. For IBM UrbanCode Deploy 7.0.x users: Plan upgrade to version 7.0.5.21 or later.
  4. 4. For IBM UrbanCode Deploy 7.1.x users: Plan upgrade to version 7.1.2.17 or later.
  5. 5. For IBM UrbanCode Deploy 7.2.x users: Plan upgrade to version 7.2.3.10 or later.
  6. 6. For IBM UrbanCode Deploy 7.3.x users: Plan upgrade to version 7.3.2.5 or later.
  7. 7. Review IBM's upgrade documentation for your specific version path.
  8. 8. Back up all current configurations and data before performing the upgrade.
Caveat Review release notes for your specific version upgrade for any compatibility or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devops Deploy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA2.0 h
24.0 hours of engineering $4,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22359 — 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-2024-22359 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