dbcve.org
Sterling Connect Direct Web ServicesApplication · Ibm

CVE-2024-45651

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-18
Fix available
A fix is available. Upgrade to 6.1.0.28 / 6.2.0.27 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 Sterling Connect:Direct Web Services 6.1.0, 6.2.0, and 6.3.0 does not invalidate session after a browser closure which could allow an authenticated user to impersonate another user on the system.

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 Sterling Connect:Direct Web Services versions 6.1.0 through 6.3.0 fail to invalidate user sessions upon browser closure. This session management flaw allows a previously authenticated user's session to remain active, potentially enabling that user or an attacker with access to the same browser to impersonate other legitimate users on the system.

MitigationImplement proper session invalidation on browser close or implement session token expiration upon logout. Additionally, consider implementing server-side session timeouts and binding sessions to additional client identifiers to reduce session hijacking risk.

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
Sterling Connect Direct Web ServicesApplication
Affected:>= 6.1.0, < 6.1.0.28>= 6.2.0, < 6.2.0.27>= 6.3.0, < 6.3.0.13

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 IBM Sterling Connect:Direct Web Services installation
    Locate the IBM Sterling Connect:Direct installation directory and look for version information in product files, manifest, or about/version utilities. Common locations include /opt/ibm/ConnectDirect or installation-specific paths.
    Affected if The product is installed and the Web Services component is present
  2. Determine the installed version of Sterling Connect:Direct Web Services
    Use the product's built-in version command, check version.info files, or access the Web Services interface and inspect the version displayed in the UI or API response.
    Affected if The version falls within any of these ranges: 6.1.0 through 6.1.0.27, 6.2.0 through 6.2.0.26, or 6.3.0 through 6.3.0.12
  3. Verify the Web Services component is enabled
    Access the Web Services endpoint (typically https://hostname:8443/cdws or similar) to confirm the web interface is active and reachable.
    Affected if The Web Services interface is accessible and the version is within the affected ranges listed above
  4. Inspect session configuration behavior
    Log into the Web Services interface, then close the browser tab without logging out. Reopen the browser and navigate to the Web Services URL to see if the previous session remains active without re-authentication.
    Affected if The session persists after browser closure without requiring re-authentication, confirming the session invalidation flaw is present

A user is affected if IBM Sterling Connect:Direct Web Services is installed with a version matching 6.1.0.x where x<28, 6.2.0.x where x<27, or 6.3.0.x where x<13, and the Web Services interface exhibits session persistence after browser closure.

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 6.1.0.28 / 6.2.0.27 / 6.3.0.13 or later
Fixed in 6.1.0.286.2.0.276.3.0.13
Interim mitigation

Implement proper session invalidation on browser close or implement session token expiration upon logout. Additionally, consider implementing server-side session timeouts and binding sessions to additional client identifiers to reduce session hijacking risk.

Recommended fix High confidence

6.1.0.28 (for 6.1.x), 6.2.0.27 (for 6.2.x), or 6.3.0.13 (for 6.3.x)

  1. Identify the currently deployed version of Sterling Connect:Direct Web Services
  2. Determine which version branch is in use (6.1.x, 6.2.x, or 6.3.x)
  3. Schedule a maintenance window for the upgrade
  4. Back up the current configuration and all user data
  5. For version 6.1.x: Upgrade to version 6.1.0.28 or later
  6. For version 6.2.x: Upgrade to version 6.2.0.27 or later
  7. For version 6.3.x: Upgrade to version 6.3.0.13 or later
  8. Apply the upgrade following IBM installation documentation
Caveat Review IBM release notes for your specific version branch to check for any configuration or compatibility changes

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

Fix this in Sterling Connect Direct Web Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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