dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2024-23558

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to 7.0.5.21 / 7.1.2.17 or later.
See remediation →
69/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
HCL DevOps Deploy / HCL Launch does not invalidate session after logout 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 · moderate confidence

HCL DevOps Deploy and HCL Launch fail to invalidate user sessions upon logout, leaving session tokens active on the server. This allows an authenticated attacker to continue using the same session identifier to impersonate other users who subsequently log in or whose sessions remain active.

MitigationImplement proper session invalidation on logout by destroying server-side session state and clearing all session tokens from the client to prevent session reuse and impersonation.

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
Hcl Devops DeployApplication
Affected:>= 8.0.0.0, < 8.0.1
Hcl LaunchApplication
Affected:>= 7.0.0.0, < 7.0.5.21>= 7.1.0.0, < 7.1.2.17>= 7.2.0.0, < 7.2.3.10>= 7.3.0.0, < 7.3.2.5

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed HCL product
    Locate the HCL DevOps Deploy or HCL Launch installation and retrieve the product version from the management console, installation directory, or version file
    Affected if The product is Hcltechsw Hcl Devops Deploy or Hcltechsw Hcl Launch
  2. Check DevOps Deploy version
    Retrieve the exact version number of HCL DevOps Deploy from the installation
    Affected if The version is >= 8.0.0.0 and < 8.0.1
  3. Check Launch version
    Retrieve the exact version number of HCL Launch from the installation
    Affected if The version falls within any of these ranges: >= 7.0.0.0 and < 7.0.5.21, OR >= 7.1.0.0 and < 7.1.2.17, OR >= 7.2.0.0 and < 7.2.3.10, OR >= 7.3.0.0 and < 7.3.2.5
  4. Review session configuration
    Inspect the server configuration files related to session management if accessible
    Affected if Session timeout or invalidation settings are present but do not enforce token destruction on logout

The environment is affected if HCL DevOps Deploy version is 8.0.0.x or HCL Launch version is within any of the vulnerable ranges listed, and the logout function does not properly invalidate server-side session state.

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.21 / 7.1.2.17 / 7.2.3.10 or later
Fixed in 7.0.5.217.1.2.177.2.3.10
Interim mitigation

Implement proper session invalidation on logout by destroying server-side session state and clearing all session tokens from the client to prevent session reuse and impersonation.

Recommended fix High confidence

HCL DevOps Deploy 8.0.1+ / HCL Launch 7.0.5.21+ / 7.1.2.17+ / 7.2.3.10+ / 7.3.2.5+ (depending on your current major version)

  1. 1. Identify the currently installed version of HCL DevOps Deploy or HCL Launch by checking the application or documentation.
  2. 2. For HCL DevOps Deploy 8.0.0.0 through 8.0.0.x: Upgrade to version 8.0.1 or later.
  3. 3. For HCL Launch 7.0.0.0 through 7.0.5.20: Upgrade to version 7.0.5.21 or later.
  4. 4. For HCL Launch 7.1.0.0 through 7.1.2.16: Upgrade to version 7.1.2.17 or later.
  5. 5. For HCL Launch 7.2.0.0 through 7.2.3.9: Upgrade to version 7.2.3.10 or later.
  6. 6. For HCL Launch 7.3.0.0 through 7.3.2.4: Upgrade to version 7.3.2.5 or later.
  7. 7. Obtain the upgrade package from HCL Support Portal (support.hcltechsw.com) and follow HCL's standard upgrade documentation.
  8. 8. After upgrade, verify that user sessions are properly invalidated upon logout by testing with a test user account.
Caveat Review HCL release notes for your specific version upgrade path as there may be compatibility considerations with existing plugins, integrations, or workflows

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

Fix this in Hcl Devops Deploy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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