Session-token disclosure via cookies lacking Secure flag
Published Oct 31, 2023 · Updated Sep 5, 2024
Sensitive cookie exposure in phpMyFAQ before 3.2.1 allows man-in-the-middle attackers to read session and CSRF tokens via HTTP requests. The Token::setSession method creates its CSRF cookie without Secure, HttpOnly, SameSite, path, or domain attributes, while Session::setCookie marks cookies Secure only when the HTTPS server value equals ON. Exposure requires a browser to revisit the deployment over HTTP after cookie issuance, placing affected tokens on the unencrypted connection.
Summary
What happened
Sensitive cookie exposure in phpMyFAQ before 3.2.1 allows man-in-the-middle attackers to read session and CSRF tokens via HTTP requests. The Token::setSession method creates its CSRF cookie without Secure, HttpOnly, SameSite, path, or domain attributes, while Session::setCookie marks cookies Secure only when the HTTPS server value equals ON. Exposure requires a browser to revisit the deployment over HTTP after cookie issuance, placing affected tokens on the unencrypted connection.
The record
- CVE
- CVE-2023-5866
- Published
- Oct 31, 2023
- Updated
- Sep 5, 2024
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-614, T1557
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 31, 2023CVE publishedPublication date reported by the CVE source.
- Sep 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=unspecified <3.2.1
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
- Huntr bounty proof of conceptproof of concept · unverified
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