CVE-2025-36360
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 · uneditedIBM UCD - IBM UrbanCode Deploy 7.1 through 7.1.2.27, 7.2 through 7.2.3.20, and 7.3 through 7.3.2.15 and IBM UCD - IBM DevOps Deploy 8.0 through 8.0.1.10, and 8.1 through 8.1.2.3 is susceptible to a race condition in http-session client-IP binding enforcement which may allow a session to be briefly reused from a new IP address before it is invalidated, potentially enabling unauthorized access under certain network conditions.
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 confidenceIBM UrbanCode Deploy and DevOps Deploy contain a race condition in HTTP session client-IP binding enforcement. The vulnerability allows a session to be briefly reused from a new IP address before invalidation occurs due to non-atomic IP validation logic. An attacker could potentially hijack a session by initiating requests from a different IP address during the brief window before the session is invalidated.
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>= 8.0.0.0, < 8.0.1.11>= 8.1.0.0, < 8.1.2.4>= 7.1.0.0, < 7.1.2.28>= 7.2.0.0, < 7.2.3.21>= 7.3.0.0, < 7.3.2.16CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionAccess the web UI and navigate to the About page (typically Help > About or /admin/about), or check the version file in the installation directory (version.txt or similar) under the product installation rootAffected if The installed version falls within any of these ranges: DevOps Deploy 8.0.0.0-8.0.1.10, 8.1.0.0-8.1.2.3; UrbanCode Deploy 7.1.0.0-7.1.2.27, 7.2.0.0-7.2.3.20, or 7.3.0.0-7.3.2.15
-
Confirm IP-based session binding is enabledCheck the server configuration files (typically server.conf or install.properties) for session security settings related to IP validation. In the web UI, navigate to Security > Session Settings and look for IP validation or IP binding optionsAffected if Session IP binding or client IP validation is explicitly enabled in the deployment server configuration
-
Verify session configuration allows IP changes during active sessionsExamine the session management configuration in the web UI under Security > Security Settings > Session settings. Check for any settings that permit or monitor IP address changes during an active authenticated sessionAffected if The server permits requests from different IP addresses to use the same session token without immediate invalidation, or if IP change monitoring is not set to immediately terminate sessions
You are affected if you are running any of the listed version ranges AND have IP-based session binding enabled, because the race condition only manifests when IP validation logic is in use but performs non-atomic checks allowing a brief window for session hijacking.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.1.2.287.2.3.217.3.2.16
Apply the vendor-supplied patches for the specific affected versions (7.1.2.28+, 7.2.3.21+, 7.3.2.16+, 8.0.1.11+, 8.1.2.4+). In the interim, implement strict network-level controls to limit IP changes for authenticated sessions and enable enhanced session monitoring.
Upgrade to the next available fix pack within your current major version branch: UrbanCode Deploy 7.1.2.28+, 7.2.3.21+, or 7.3.2.16+; DevOps Deploy 8.0.1.11+ or 8.1.2.4+
- 1. Identify the current version of IBM UrbanCode Deploy or IBM DevOps Deploy installed in your environment
- 2. Determine which version branch is in use (7.1.x, 7.2.x, 7.3.x for UrbanCode Deploy or 8.0.x, 8.1.x for DevOps Deploy)
- 3. For UrbanCode Deploy 7.1.x: upgrade to version 7.1.2.28 or later
- 4. For UrbanCode Deploy 7.2.x: upgrade to version 7.2.3.21 or later
- 5. For UrbanCode Deploy 7.3.x: upgrade to version 7.3.2.16 or later
- 6. For DevOps Deploy 8.0.x: upgrade to version 8.0.1.11 or later
- 7. For DevOps Deploy 8.1.x: upgrade to version 8.1.2.4 or later
- 8. After upgrade, verify the fix by reviewing IBM's release notes for the specific fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-36360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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