Forced logout via missing CSRF token validation
Published Dec 30, 2023 · Updated Aug 5, 2024
Cross-site request forgery in Petr Kirpeit's OwnHealthRecord 0.1-alpha through 0.3.1-alpha allows remote attackers to terminate user sessions. The includes/logout.php handler destroys the active session without first verifying that the request carries the session's CSRF token. An attacker must induce a signed-in user's browser to submit the request; the demonstrated consequence is forced logout, not access to health data.
Summary
What happened
Cross-site request forgery in Petr Kirpeit's OwnHealthRecord 0.1-alpha through 0.3.1-alpha allows remote attackers to terminate user sessions. The includes/logout.php handler destroys the active session without first verifying that the request carries the session's CSRF token. An attacker must induce a signed-in user's browser to submit the request; the demonstrated consequence is forced logout, not access to health data.
The record
- CVE
- CVE-2018-25096
- Published
- Dec 30, 2023
- Updated
- Aug 5, 2024
- Vendor
- Petr Kirpeit
- Product
- OwnHealthRecord
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2023CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1-alpha
- Affected versionversion=0.2-alpha
- Affected versionversion=0.3.1-alpha
- Affected versionversion=0.3-alpha
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.
Weakness, pattern, technique
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