Cyber Resilience

CVE-2024-42207

Auth Bypass in Hcltech Dryice Iautomate 6.4.2

Published
05 February 2025
Modified
10 October 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L
EPSS Score 0.0027 19th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-42207 is a medium-severity Session Fixation (CWE-384) vulnerability in Hcltech Dryice Iautomate. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Web Session Cookie (T1539); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and AC-12 (Session Termination) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

HCL iAutomate is affected by a session fixation vulnerability.  An attacker could hijack a victim's session ID from their authenticated session.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1550.004 Web Session Cookie Lateral Movement
Adversaries can use stolen session cookies to authenticate to web applications and services.
T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-31952Same product: Hcltech Dryice Iautomate
CVE-2025-31955Same product: Hcltech Dryice Iautomate
CVE-2025-31954Same product: Hcltech Dryice Iautomate
CVE-2025-0253Same vendor: Hcltech
CVE-2024-42170Same vendor: Hcltech
CVE-2024-42171Same vendor: Hcltech
CVE-2025-55266Same vendor: Hcltech
CVE-2025-0251Same vendor: Hcltech
CVE-2023-23347Same product: Hcltech Dryice Iautomate
CVE-2025-31953Same product: Hcltech Dryice Iautomate

Affected Assets

hcltech
dryice iautomate
6.4.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.4.4
  • V7.6.2

Mitigating Controls (NIST 800-53 r5) AI

Requires protection of session authenticity, which directly stops an attacker from using a stolen or fixed session identifier after authentication.

Limits the lifetime of any session (fixed or not), thereby reducing the window during which a stolen identifier remains usable.

Enforces that only properly authorized (i.e., freshly authenticated) sessions can access resources, making a pre-existing fixed session ID unusable.

Forces re-authentication under defined conditions, which should result in issuance of a fresh session identifier and invalidation of any prior one.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Proper authentication processes must invalidate prior session identifiers to prevent fixation attacks.

PR.AA-01 partial match
prevents

Managing identities and credentials includes handling session identifiers as temporary credentials that must be invalidated on re-authentication.

PR.AA-04 partial match
prevents

Protecting and verifying identity assertions encompasses secure handling and regeneration of session tokens.

PR.PS-01 partial match
prevents

Configuration baselines can enforce session regeneration and timeout settings that block fixation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect session-fixation issues, yet the weakness absence does not replace comprehensive testing.

degrades

Access-control policy can mandate session invalidation on re-authentication, but does not prescribe the technical mechanism.

degrades

Identity-management procedures can require new session tokens after login, yet the control is broader than session handling.

degrades

Authentication-information rules can include session-token lifecycle requirements, but the control focuses on credential management.

prevents

Secure-SDLC requirement can embed session-fixation checks, but eliminating the weakness does not satisfy the full SDLC control.

prevents

Application-security requirements can specify session handling, yet the weakness fix alone does not meet the broader requirement.

References