Unauthenticated session hijacking via reused identifier
Published Feb 6, 2020 · Updated Aug 6, 2024
Session management in CGILua 5.1.x allows remote attackers to hijack arbitrary user sessions through a reused session identifier. The session.lua identifier generator returns the same value for every session rather than creating a unique, unpredictable value. No authentication is required, but a victim session must exist; presenting the shared identifier grants access to that session's application privileges and data.
Summary
What happened
Session management in CGILua 5.1.x allows remote attackers to hijack arbitrary user sessions through a reused session identifier. The session.lua identifier generator returns the same value for every session rather than creating a unique, unpredictable value. No authentication is required, but a victim session must exist; presenting the shared identifier grants access to that session's application privileges and data.
The record
- CVE
- CVE-2014-10399
- Published
- Feb 6, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
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