dbcve.org
Devops DeployApplication · Ibm

CVE-2024-55904

HIGH · 7.2 CVSS v3.1 Published 2025-02-14
Fix available
A fix is available. Upgrade to 7.0.5.26 / 7.1.2.22 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 DevOps Deploy 8.0 through 8.0.1.4, 8.1 through 8.1.0.0 / IBM UrbanCode Deploy 7.0 through 7.0.5.25, 7.1 through 7.1.2.21, 7.2 through 7.2.3.14, and 7.3 through 7.3.2.9 could allow a remote privileged authenticated attacker to execute arbitrary commands on the system by sending specially crafted input containing special elements.

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

This is an authenticated command injection vulnerability in IBM DevOps Deploy and UrbanCode Deploy. A remote privileged attacker can execute arbitrary OS commands by sending specially crafted input containing special elements, likely through insufficient input validation in certain application functions.

MitigationApply the vendor patches for the affected versions (8.0.1.5, 8.1.0.1, 7.0.5.26, 7.1.2.22, 7.2.3.15, and 7.3.2.10). If immediate patching is not possible, restrict network access to the deployment interface to trusted users only.

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.5= 8.1.0.0
Urbancode DeployApplication
Affected:>= 7.0.0.0, < 7.0.5.26>= 7.1.0.0, < 7.1.2.22>= 7.2.0.0, < 7.2.3.15>= 7.3.0.0, < 7.3.2.10

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 if IBM DevOps Deploy or UrbanCode Deploy is installed
    Check for running processes or services named 'ibm-ucd', 'urbancode', 'devops-deploy', or look in common installation directories such as /opt/ibm/uddeploy or /opt/ibm/dd. On Windows, check Program Files for IBM UrbanCode Deploy or IBM DevOps Deploy folders.
    Affected if The software is present on the system
  2. Determine the installed version of IBM DevOps Deploy
    Check the version.info file typically located in the installation root directory, or use the version command if available via the command line interface. For version 8.x, look for a file named 'version.info' in the installation directory.
    Affected if The installed version is 8.0.0.0 through 8.0.1.4 inclusive, or exactly 8.1.0.0
  3. Determine the installed version of IBM UrbanCode Deploy
    Check the version.info file in the installation root directory, or use the version command if available via the command line interface. For versions 7.x, look in the same location as the version.info file.
    Affected if The installed version falls within these ranges: 7.0.0.0 through 7.0.5.25, 7.1.0.0 through 7.1.2.21, 7.2.0.0 through 7.2.3.14, or 7.3.0.0 through 7.3.2.9
  4. Verify if authentication is enabled on the deployment interface
    Check the installed configuration files for the authentication settings. In the conf or etc directory of the installation, examine the app.properties or security.xml file to determine if user authentication is properly configured and enabled.
    Affected if Authentication is disabled, misconfigured, or accessible to untrusted users
  5. Assess network exposure of the deployment web interface
    Review firewall rules and network configuration to determine if the UrbanCode Deploy or DevOps Deploy web interface (default ports 8080, 8443) is exposed to untrusted networks. Check if the listener is bound to 0.0.0.0 or an externally accessible IP address.
    Affected if The web interface is accessible from untrusted network segments or the internet

The environment is affected if IBM DevOps Deploy version 8.0.0.0-8.0.1.4 or 8.1.0.0, or UrbanCode Deploy version 7.0.0.0-7.0.5.25, 7.1.0.0-7.1.2.21, 7.2.0.0-7.2.3.14, or 7.3.0.0-7.3.2.9 is installed AND the web interface with authentication is reachable by the attacker.

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.26 / 7.1.2.22 / 7.2.3.15 or later
Fixed in 7.0.5.267.1.2.227.2.3.15
Interim mitigation

Apply the vendor patches for the affected versions (8.0.1.5, 8.1.0.1, 7.0.5.26, 7.1.2.22, 7.2.3.15, and 7.3.2.10). If immediate patching is not possible, restrict network access to the deployment interface to trusted users only.

Recommended fix High confidence

IBM DevOps Deploy 8.0.1.5+ / 8.1.0.1+; IBM UrbanCode Deploy 7.0.5.26+ / 7.1.2.22+ / 7.2.3.15+ / 7.3.2.10+

  1. 1. Identify the specific IBM DevOps Deploy or UrbanCode Deploy version currently installed
  2. 2. For DevOps Deploy 8.0.x versions: upgrade to version 8.0.1.5 or later
  3. 3. For DevOps Deploy 8.1.0.0: upgrade to version 8.1.0.1 or later (or the next available stable release)
  4. 4. For UrbanCode Deploy 7.0.x: upgrade to version 7.0.5.26 or later
  5. 5. For UrbanCode Deploy 7.1.x: upgrade to version 7.1.2.22 or later
  6. 6. For UrbanCode Deploy 7.2.x: upgrade to version 7.2.3.15 or later
  7. 7. For UrbanCode Deploy 7.3.x: upgrade to version 7.3.2.10 or later
  8. 8. After upgrade, verify the installation and test critical workflows
Caveat Review IBM's upgrade documentation for version-specific migration notes and compatibility considerations

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

Fix this in Devops Deploy Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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