Authenticated session hijacking via session fixation
Published Feb 5, 2025 · Updated Feb 5, 2025
Session fixation in HCL iAutomate 6.4.2 allows remote authenticated users to hijack a victim's authenticated session. HCL has not published the affected component or the operation that permits a session identifier to remain fixed across authentication. The attacker must already hold high privileges, and successful exploitation transfers access to the victim's authenticated session.
Summary
What happened
Session fixation in HCL iAutomate 6.4.2 allows remote authenticated users to hijack a victim's authenticated session. HCL has not published the affected component or the operation that permits a session identifier to remain fixed across authentication. The attacker must already hold high privileges, and successful exploitation transfers access to the victim's authenticated session.
The record
- CVE
- CVE-2024-42207
- Published
- Feb 5, 2025
- Updated
- Feb 5, 2025
- Vendor
- HCL Software
- Product
- HCL iAutomate
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 5, 2025CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo