dbcve.org
Devops DeployApplication · Ibm

CVE-2024-28781

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 7.0.5.21 / 7.1.2.17 or later.
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 (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 8.0 through 8.0.0.1 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 X-Force ID: 285654.

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

IBM UrbanCode Deploy contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code through user input fields, which executes when other users view the affected content. This can lead to credential disclosure or session hijacking within trusted sessions.

MitigationApply vendor patches when available. Immediate mitigations include implementing strict Content Security Policy (CSP) headers, enabling XSS protection in browsers, and sanitizing user-supplied input in Web UI components.

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

CVSS:3.1/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. Verify IBM UrbanCode Deploy Web UI is accessible
    Attempt to access the Web UI login page at the standard endpoint (typically https://hostname:8443 or similar port). If the login page loads, the Web UI is enabled.
    Affected if The Web UI is accessible and an attacker could potentially submit malicious input through user input fields.
  2. Identify the installed product version
    Check the product version through the Web UI by logging in and navigating to the About page, or check the version file in the installation directory if you have server access.
    Affected if The version falls within any of these ranges: IBM DevOps Deploy >= 8.0.0.0 and < 8.0.1.0; IBM UrbanCode Deploy >= 7.0.0.0 and < 7.0.5.21, >= 7.1.0.0 and < 7.1.2.17, >= 7.2.0.0 and < 7.2.3.10, or >= 7.3.0.0 and < 7.3.2.5
  3. Confirm user input fields exist in the Web UI
    Log into the Web UI and identify fields that accept user-supplied text, such as component names, application descriptions, process properties, or resource tags.
    Affected if User input fields are present and the application does not sanitize special characters before rendering them back to users.

Your environment is affected if the IBM UrbanCode Deploy or IBM DevOps Deploy Web UI is accessible and the installed version matches any of the vulnerable version ranges listed.

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 vendor patches when available. Immediate mitigations include implementing strict Content Security Policy (CSP) headers, enabling XSS protection in browsers, and sanitizing user-supplied input in Web UI components.

Recommended fix High confidence

Upgrade to: 8.0.1.0 for 8.0.x, 7.0.5.21 for 7.0.x, 7.1.2.17 for 7.1.x, 7.2.3.10 for 7.2.x, or 7.3.2.5 for 7.3.x

  1. 1. Identify the currently installed IBM UrbanCode Deploy or DevOps Deploy version by checking the application UI or release documentation
  2. 2. Determine the appropriate upgrade path based on your current major.minor version (7.0.x, 7.1.x, 7.2.x, 7.3.x, or 8.0.x)
  3. 3. Download the corresponding fixed version from IBM Fix Central or your authorized IBM distribution channel
  4. 4. Review IBM's official upgrade documentation for UrbanCode Deploy
  5. 5. Perform a backup of the current installation including the database and configuration files
  6. 6. Schedule a maintenance window as upgrades may require downtime
  7. 7. Execute the upgrade following IBM's standard upgrade procedures
  8. 8. After upgrade, verify the new version is installed correctly
Caveat Standard upgrade risks apply: review compatibility with existing plugins, integrations, and custom scripts; test in non-production environment first

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

Fix this in Devops Deploy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
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,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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