Account hijacking via unreplaced pre-authentication session identifier
Published Feb 18, 2021 · Updated Aug 4, 2024
Session fixation in the Pi-hole web interface 5.0, 5.1, and 5.1.1 allows remote attackers to hijack accounts via PHPSESSID. The login endpoint accepts a PHPSESSID cookie chosen before authentication and retains that identifier after a victim signs in. Exploitation requires user interaction to place the chosen cookie in an authenticated victim's browser; reuse of the identifier grants access to that active account session.
Summary
What happened
Session fixation in the Pi-hole web interface 5.0, 5.1, and 5.1.1 allows remote attackers to hijack accounts via PHPSESSID. The login endpoint accepts a PHPSESSID cookie chosen before authentication and retains that identifier after a victim signs in. Exploitation requires user interaction to place the chosen cookie in an authenticated victim's browser; reuse of the identifier grants access to that active account session.
The record
- CVE
- CVE-2020-35591
- Published
- Feb 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 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.
Public exploit references
- Pi-hole session-fixation proof of conceptfunctional · 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