Session hijacking via unreplaced session identifiers
Published Jun 11, 2023 · Updated Jan 6, 2025
Session fixation in Froxlor before 2.1.0 allows remote attackers to hijack authenticated panel sessions through a fixed session ID. The finishLogin path and administrator user-switch actions retain the prior PHP session identifier instead of regenerating it when identity changes. Exploitation requires a victim to authenticate or an administrator to switch users with an identifier already known to the attacker, enabling access within that session's privileges.
Summary
What happened
Session fixation in Froxlor before 2.1.0 allows remote attackers to hijack authenticated panel sessions through a fixed session ID. The finishLogin path and administrator user-switch actions retain the prior PHP session identifier instead of regenerating it when identity changes. Exploitation requires a victim to authenticate or an administrator to switch users with an identifier already known to the attacker, enabling access within that session's privileges.
The record
- CVE
- CVE-2023-3192
- Published
- Jun 11, 2023
- Updated
- Jan 6, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 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=unspecified <2.1.0
What conditions does exploitation require?
What is affected?
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