dbcve.org
Hcl NomadApplication · Hcltech

CVE-2024-23586

HIGH · 7.5 CVSS v3.1 Published 2024-09-27
Fix available
A fix is available. Upgrade to 1.0.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
HCL Nomad is susceptible to an insufficient session expiration vulnerability.   Under certain circumstances, an unauthenticated attacker could obtain old session information.

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 Nomad fails to properly invalidate or expire session tokens after logout or timeout. Under certain conditions, unauthenticated attackers can obtain and reuse old session information, potentially hijacking valid user sessions.

MitigationImplement proper session expiration, ensure all session tokens are invalidated upon logout, and rotate session identifiers after authentication. Apply vendor patches when available.

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 NomadApplication
Affected:< 1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed HCL Nomad version
    Locate the HCL Nomad installation and determine its version number (typically visible in the application, installation directory, or about dialog)
    Affected if The installed version is lower than 1.0.13 (e.g., 1.0.12, 1.0.10, etc.)
  2. Examine session timeout configuration
    Check the session or security configuration settings within the Nomad deployment for session timeout values and expiration policies
    Affected if Session timeout is set to an unusually long duration, or no explicit timeout is configured
  3. Review session token handling after logout
    Test the application behavior: authenticate, perform actions, log out, then attempt to use the previous session identifier or token
    Affected if Old session identifiers remain valid after logout and can be reused to access the application
  4. Inspect session configuration files
    Locate and examine any configuration files related to session management (check installation directory or config folder for files mentioning session, token, or authentication settings)
    Affected if No session invalidation or token rotation settings are present in the configuration, or weak session policies are defined
  5. Verify session token uniqueness after re-authentication
    Log in multiple times and compare the session identifiers or tokens generated for each new session
    Affected if New sessions receive identical or predictable session identifiers instead of unique, randomized tokens

The environment is affected if HCL Nomad version is below 1.0.13 AND session tokens remain valid after logout or timeout, allowing potential reuse by an attacker.

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 1.0.13 or later
Fixed in 1.0.13
Interim mitigation

Implement proper session expiration, ensure all session tokens are invalidated upon logout, and rotate session identifiers after authentication. Apply vendor patches when available.

Recommended fix Moderate confidence

1.0.13

  1. Download HCL Nomad version 1.0.13 or later from the official HCL support portal
  2. Back up your current HCL Nomad installation and configuration
  3. Stop the HCL Nomad service
  4. Install the upgraded version (1.0.13 or later)
  5. Verify the installation was successful
  6. Restart the HCL Nomad service

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

Fix this in Hcl Nomad 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-23586 — 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-23586 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