Account hijacking via unreplaced login session ID
Published May 27, 2021 · Updated Aug 3, 2024
Session fixation in CubeCart 6.4.2 allows remote authenticated users to hijack a victim's account through an attacker-chosen cookie. The user and administrator login paths bind the authenticated account to the existing session ID instead of regenerating it. Exploitation requires planting a known cookie before the victim logs in; that cookie then grants the victim's account privileges.
Summary
What happened
Session fixation in CubeCart 6.4.2 allows remote authenticated users to hijack a victim's account through an attacker-chosen cookie. The user and administrator login paths bind the authenticated account to the existing session ID instead of regenerating it. Exploitation requires planting a known cookie before the victim logs in; that cookie then grants the victim's account privileges.
The record
- CVE
- CVE-2021-33394
- Published
- May 27, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, CAPEC-61, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Session Fixation in Cubecart 6.4.2proof 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