Session hijacking via URL-exposed authentication tokens
Published Mar 5, 2021 · Updated Sep 17, 2024
Information exposure in Secomea GateManager before 9.4 allows remote attackers to hijack authenticated sessions through leaked tokens. After login, its web GUI places the authentication token in the URL path of every subsequent GET and POST request, exposing it to browser history, Referer headers, and web logs. Exploitation requires obtaining a recorded or forwarded URL from an authenticated user's session; the token alone opens restricted pages with that session's authority.
Summary
What happened
Information exposure in Secomea GateManager before 9.4 allows remote attackers to hijack authenticated sessions through leaked tokens. After login, its web GUI places the authentication token in the URL path of every subsequent GET and POST request, exposing it to browser history, Referer headers, and web logs. Exploitation requires obtaining a recorded or forwarded URL from an authenticated user's session; the token alone opens restricted pages with that session's authority.
The record
- CVE
- CVE-2020-29030
- Published
- Mar 5, 2021
- Updated
- Sep 17, 2024
- Vendor
- Secomea
- Product
- GateManager
- Classifications
- CWE-352, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=All <9.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Tenable authentication-token path proof of conceptproof 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