Account takeover via reused preauthentication session identifier
Published May 18, 2020 · Updated Aug 4, 2024
Session fixation in rConfig 3.9.4 allows remote attackers to take over a user's account by forcing a chosen PHPSESSID. The login flow preserves the preauthentication session identifier instead of expiring it and issuing a fresh randomized value. Exploitation requires a victim to authenticate with an attacker-chosen cookie, demonstrated by chaining either cited cross-site scripting flaw.
Summary
What happened
Session fixation in rConfig 3.9.4 allows remote attackers to take over a user's account by forcing a chosen PHPSESSID. The login flow preserves the preauthentication session identifier instead of expiring it and issuing a fresh randomized value. Exploitation requires a victim to authenticate with an attacker-chosen cookie, demonstrated by chaining either cited cross-site scripting flaw.
The record
- CVE
- CVE-2020-12258
- Published
- May 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2020CVE 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.
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.
Weakness, pattern, technique
Public exploit references
- rConfig 3.9.4 session-fixation 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