Account takeover via preserved attacker-chosen session identifier
Published Jun 22, 2021 · Updated Aug 4, 2024
Session fixation in IceHrm 29.0.0.OS allows remote attackers to hijack a valid user's authenticated session through a crafted cookie. The login flow preserves an attacker-chosen PHPSESSID instead of replacing it with a new identifier after the victim authenticates. Exploitation requires user interaction to set the known cookie and authenticate; reuse of that identifier grants the attacker the victim's account access.
Summary
What happened
Session fixation in IceHrm 29.0.0.OS allows remote attackers to hijack a valid user's authenticated session through a crafted cookie. The login flow preserves an attacker-chosen PHPSESSID instead of replacing it with a new identifier after the victim authenticates. Exploitation requires user interaction to set the known cookie and authenticate; reuse of that identifier grants the attacker the victim's account access.
The record
- CVE
- CVE-2021-35046
- Published
- Jun 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, CAPEC-61, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- IceHrm 29.0.0.OS session-fixation account-takeover proof of conceptproof of concept · demonstrated
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