dbcve.org
Devops DeployApplication · Ibm

CVE-2024-54176

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-08
Fix available
A fix is available. Upgrade to 7.0.5.26 / 7.1.2.22 or later.
See remediation →
71/100
Remediation priority · Elevated
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 and IBM UrbanCode Deploy (UCD) 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 could allow an authenticated user to obtain sensitive information about other users on the system due to missing authorization for a function.

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 DevOps Deploy and UrbanCode Deploy contain a missing authorization vulnerability where an authenticated user can access sensitive information about other users on the system. An attacker with basic credentials can enumerate or view user profile data (potentially including names, emails, roles, or other attributes) that should be restricted to authorized administrators. This is an information disclosure via broken access control (CWE-200).

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.3 or later) which add proper authorization checks to the vulnerable function.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 IBM deployment product
    Locate the product installation directory and look for version manifest or about dialog. Common paths: /opt/ibm/ucd or /opt/ibm/udd. Check for version.txt, about.html, or use the product's version command if available.
    Affected if The product is IBM DevOps Deploy or IBM UrbanCode Deploy
  2. Determine the exact version number
    Read the version from installation files. Typical locations: <install_dir>/bin/version.properties, <install_dir>/etc/version, or access the /about endpoint in the web UI if available.
    Affected if The exact version cannot be determined or differs from installed product files
  3. Compare DevOps Deploy version against affected ranges
    For IBM DevOps Deploy, check if version is >= 8.0.0.0 AND < 8.0.1.5, OR equals exactly 8.1.0.0. Note: versions 8.0.1.5 through 8.1.0.0 (excluding 8.1.0.0) are NOT affected.
    Affected if Version falls within >= 8.0.0.0 to < 8.0.1.5 OR equals 8.1.0.0
  4. Compare UrbanCode Deploy version against affected ranges
    For IBM UrbanCode Deploy, check if version falls in any of these ranges: >= 7.0.0.0 to < 7.0.5.26, >= 7.1.0.0 to < 7.1.2.22, >= 7.2.0.0 to < 7.2.3.15, OR >= 7.3.0.0 to < 7.3.2.10.
    Affected if Version matches any of the four affected version ranges listed

You are affected if the installed product is IBM DevOps Deploy version 8.0.0.0 through 8.0.1.4 or exactly 8.1.0.0, OR IBM UrbanCode Deploy version 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.

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.3 or later) which add proper authorization checks to the vulnerable function.

Recommended fix High confidence

IBM DevOps Deploy 8.0.1.5+ (8.0.x) or 8.1.0.1+ (8.1.x); IBM UrbanCode Deploy 7.0.5.26+, 7.1.2.22+, 7.2.3.15+, or 7.3.2.10+

  1. 1. Identify the currently installed IBM DevOps Deploy or UrbanCode Deploy version using the product's version information.
  2. 2. For DevOps Deploy 8.0.x versions (8.0.0.0 through 8.0.1.4): Plan upgrade to version 8.0.1.5 or later.
  3. 3. For DevOps Deploy version 8.1.0.0: Plan upgrade to version 8.1.0.1 or later.
  4. 4. For UrbanCode Deploy 7.0.x versions (7.0.0.0 through 7.0.5.25): Plan upgrade to version 7.0.5.26 or later.
  5. 5. For UrbanCode Deploy 7.1.x versions (7.1.0.0 through 7.1.2.21): Plan upgrade to version 7.1.2.22 or later.
  6. 6. For UrbanCode Deploy 7.2.x versions (7.2.0.0 through 7.2.3.14): Plan upgrade to version 7.2.3.15 or later.
  7. 7. For UrbanCode Deploy 7.3.x versions (7.3.0.0 through 7.3.2.9): Plan upgrade to version 7.3.2.10 or later.
  8. 8. Obtain the appropriate fix from IBM Fix Central (https://www.ibm.com/support/fixcentral) or via your IBM entitlement.
Caveat Review IBM's release notes for the target version to check for any compatibility issues or configuration changes that may affect your existing deployments

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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