dbcve.org
Urbancode DeployApplication · Ibm

CVE-2024-45091

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 7.0.5.25 / 7.1.2.21 or later.
See remediation →
57/100
Remediation priority · Elevated
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.0 through 7.0.5.24, 7.1 through 7.1.2.10, and 7.2 through 7.2.3.13 stores potentially sensitive information in log files that could be read by a local user with access to HTTP request logs.

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 versions 7.0-7.0.5.24, 7.1-7.1.2.10, and 7.2-7.2.3.13 stores potentially sensitive HTTP request information (such as credentials, tokens, or PII) in log files that can be read by local users with access to HTTP request logs, representing an information disclosure vulnerability.

MitigationUpdate to a patched version if available, or implement log sanitization/filtering to prevent sensitive data from being written to logs, and ensure strict access controls on log directories.

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
Urbancode DeployApplication
Affected:>= 7.0.0.0, < 7.0.5.25>= 7.1.0.0, < 7.1.2.21>= 7.2.0.0, < 7.2.3.14

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

CVSS:3.1/AV:L/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 UrbanCode Deploy version
    Check the version file or startup logs typically located in the installation directory under /opt/ibm-ucd or the system service information. Run: ucd-server --version or inspect the manifest.properties file in the installation root.
    Affected if The installed version falls within 7.0.0.0 to 7.0.5.24, 7.1.0.0 to 7.1.2.10, or 7.2.0.0 to 7.2.3.13.
  2. Confirm HTTP request logging is enabled
    Inspect the server configuration file (typically server.xml or install.properties) for logging settings related to HTTP requests. Look for flags like 'http.log.enabled' or 'request.logging' set to true.
    Affected if HTTP request logging is explicitly enabled in the configuration.
  3. Locate the HTTP request log files
    Navigate to the default log directory (commonly /var/log/ibm-ucd or <install_dir>/var/log) and identify log files such as http_access.log, request.log, or http.log.
    Affected if HTTP request log files exist in the system.
  4. Inspect log files for sensitive data patterns
    Use grep or a text search to scan the log files for patterns matching credentials (password=, token=, Authorization:), session identifiers, or common PII patterns like email addresses or social security number formats.
    Affected if Log files contain plain-text credentials, tokens, Authorization headers, or other sensitive data that should not be exposed.
  5. Check access controls on log directories
    Review file system permissions on the log directory using 'ls -la' or equivalent commands. Verify which OS users and groups have read access to the log files.
    Affected if Log directory permissions allow access by users other than the dedicated application service account (world-readable or group-readable by non-admin users).

You are affected if your IBM UrbanCode Deploy version is within the vulnerable ranges AND HTTP request logging is enabled, making sensitive data potentially readable by unauthorized local users.

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.25 / 7.1.2.21 / 7.2.3.14 or later
Fixed in 7.0.5.257.1.2.217.2.3.14
Interim mitigation

Update to a patched version if available, or implement log sanitization/filtering to prevent sensitive data from being written to logs, and ensure strict access controls on log directories.

Recommended fix High confidence

Upgrade to 7.0.5.25+ (if on 7.0.x), 7.1.2.21+ (if on 7.1.x), or 7.2.3.14+ (if on 7.2.x)

  1. 1. Identify the current IBM UrbanCode Deploy version by checking the UCD server or administration console.
  2. 2. Determine which version branch you are currently running (7.0.x, 7.1.x, or 7.2.x).
  3. 3. For version 7.0.x: Plan upgrade to version 7.0.5.25 or later.
  4. 4. For version 7.1.x: Plan upgrade to version 7.1.2.21 or later.
  5. 5. For version 7.2.x: Plan upgrade to version 7.2.3.14 or later.
  6. 6. Review IBM's upgrade documentation and perform a full backup of the current installation before upgrading.
  7. 7. Apply the upgrade following IBM's standard upgrade procedures for UrbanCode Deploy.
  8. 8. After upgrade, verify the version number reflects the patched release.
Caveat Standard IBM UrbanCode Deploy upgrade considerations apply; review release notes for any compatibility or configuration changes between versions

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

Fix this in Urbancode Deploy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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