dbcve.org
Devops DeployApplication · Ibm

CVE-2024-56469

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to 7.1.2.23 / 7.2.3.16 or later.
See remediation →
68/100
Remediation priority · Elevated
No privileges 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 UrbanCode Deploy (UCD) 7.1 through 7.1.2.22, 7.2 through 7.2.3.15, and 7.3 through 7.3.2.10 / IBM DevOps Deploy 8.0 through 8.0.1.5 and 8.1 through 8.1.0.1 could allow unauthorized access to other services or potential exposure of sensitive data due to missing authentication in its Agent Relay service.

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 and DevOps Deploy contain a missing authentication vulnerability in the Agent Relay service across versions 7.1-7.3.2.10 and 8.0-8.1.0.1. The Agent Relay service, which handles communication between agents and the UCD server, does not properly authenticate requests, potentially allowing unauthorized access to other services or exposure of sensitive data.

MitigationApply the vendor-supplied patches for the affected versions (7.1.2.23, 7.2.3.16, 7.3.2.11, 8.0.1.6, 8.1.0.2) or upgrade to a fixed version. If patches are unavailable, implement network segmentation and access controls around the Agent Relay service.

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.1.0.0, < 7.1.2.23>= 7.2.0.0, < 7.2.3.16>= 7.3.0.0, < 7.3.2.11

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

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

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 product and version
    Locate the IBM UrbanCode Deploy or DevOps Deploy installation directory and check the version file (typically in the installation root or through the web UI's About page). Common paths include /opt/ibm/ucd or the product's home directory. Use the command: ls -la <install_dir>/version.txt or access the web UI at https://<server>:8443/ and navigate to Settings > About.
    Affected if The installed version falls within these ranges: DevOps Deploy 8.0.0.0 through 8.0.1.4, or exactly 8.1.0.0; UrbanCode Deploy 7.1.0.0-7.1.2.22, 7.2.0.0-7.2.3.15, or 7.3.0.0-7.3.2.10.
  2. Confirm the Agent Relay component is in use
    Check if the Agent Relay service is installed and enabled. This is typically a separate component that can be installed alongside the UCD server. Look for the 'agent-relay' directory in the installation path or check for processes named 'agentrelay' running on the system. Inspect the file <install_dir>/agent-relay/conf/agentrelay.properties if the directory exists.
    Affected if The Agent Relay service is present and configured on the system.
  3. Verify Agent Relay network exposure
    Review the Agent Relay configuration file (<install_dir>/agent-relay/conf/agentrelay.properties) for the server.port setting (default 20080 for HTTP or 20443 for HTTPS). Check if this port is bound to a public or unrestricted network interface rather than localhost or an internal network address.
    Affected if The Agent Relay port is accessible from untrusted networks or the binding address is set to 0.0.0.0 without proper firewall rules.
  4. Inspect Agent Relay authentication configuration
    Examine the agentrelay.properties file for any authentication-related settings. Look for properties like 'agent relay.authentication.enabled' or similar flags. Also check the server.xml or bootstrap.xml files in the agent-relay/conf directory for security constraint configurations.
    Affected if Authentication for the Agent Relay service is explicitly disabled, or no authentication mechanism is configured.

A user is affected if they have UrbanCode Deploy or DevOps Deploy with an Agent Relay component running and the installed version falls within the affected version ranges listed in the CVE.

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.1.2.23 / 7.2.3.16 / 7.3.2.11 or later
Fixed in 7.1.2.237.2.3.167.3.2.11
Interim mitigation

Apply the vendor-supplied patches for the affected versions (7.1.2.23, 7.2.3.16, 7.3.2.11, 8.0.1.6, 8.1.0.2) or upgrade to a fixed version. If patches are unavailable, implement network segmentation and access controls around the Agent Relay service.

Recommended fix High confidence

IBM DevOps Deploy 8.0.1.5+/8.1.0.2+ or IBM UrbanCode Deploy 7.1.2.23+/7.2.3.16+/7.3.2.11+

  1. 1. Identify the currently installed IBM DevOps Deploy or UrbanCode Deploy version by checking the product's About or version information.
  2. 2. For IBM DevOps Deploy 8.0.x users: Upgrade to version 8.0.1.5 or later.
  3. 3. For IBM DevOps Deploy 8.1.x users: Upgrade to version 8.1.0.2 or later.
  4. 4. For IBM UrbanCode Deploy 7.1.x users: Upgrade to version 7.1.2.23 or later.
  5. 5. For IBM UrbanCode Deploy 7.2.x users: Upgrade to version 7.2.3.16 or later.
  6. 6. For IBM UrbanCode Deploy 7.3.x users: Upgrade to version 7.3.2.11 or later.
  7. 7. After upgrading, verify that the Agent Relay service now requires proper authentication.
  8. 8. Test that legitimate agent communications work correctly with the authenticated Agent Relay service.
Caveat Review IBM's migration/upgrade documentation for any compatibility notes between major versions; ensure agent configurations are updated to use authentication if not already configured

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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