Account takeover via reused session identifiers
Published Jun 24, 2020 · Updated Aug 4, 2024
Session fixation in playSMS 1.4.3 and earlier allows remote attackers to take control of user accounts through a reused PHPSESSID cookie. The login flow retains the same PHPSESSID value before and after authentication instead of regenerating the session identifier. Exploitation requires an attacker to fix a known session in a victim's browser and the victim to authenticate, after which the attacker can act with that account's privileges.
Summary
What happened
Session fixation in playSMS 1.4.3 and earlier allows remote attackers to take control of user accounts through a reused PHPSESSID cookie. The login flow retains the same PHPSESSID value before and after authentication instead of regenerating the session identifier. Exploitation requires an attacker to fix a known session in a victim's browser and the victim to authenticate, after which the attacker can act with that account's privileges.
The record
- CVE
- CVE-2020-15018
- Published
- Jun 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, CAPEC-61, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 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.
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 reproduction stepsproof 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