Unauthenticated session hijacking via brute-forceable cookies
Published Dec 13, 2021 · Updated Aug 4, 2024
Session hijacking in Reprise RLM 14.2 allows remote attackers to read authorized web content through a guessed active-session cookie. The web interface exposes the static cookie name, then accepts attacker-supplied values from a four-hex-character space on Windows. No credentials or user interaction are required, but a legitimate user must have an active session; Linux cookies appear to use eight characters.
Summary
What happened
Session hijacking in Reprise RLM 14.2 allows remote attackers to read authorized web content through a guessed active-session cookie. The web interface exposes the static cookie name, then accepts attacker-supplied values from a four-hex-character space on Windows. No credentials or user interaction are required, but a legitimate user must have an active session; Linux cookies appear to use eight characters.
The record
- CVE
- CVE-2021-44151
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1606.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 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.
Weakness, pattern, technique
Public exploit references
- Reprise License Manager 14.2 Session Hijackingproof 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