Authenticated session hijacking via timestamp-derived identifiers
Published Mar 30, 2022 · Updated Jul 9, 2026
Authentication bypass in Totolink A3100R 5.9c.4577 allows remote authenticated users to hijack a valid web-management session. The web configuration constructs SESSION_ID as 2::2, exposing a small, time-derived token space instead of an unpredictable identifier. A valid session must exist, and successful timestamp brute forcing grants that session's management privileges and configuration capabilities.
Summary
What happened
Authentication bypass in Totolink A3100R 5.9c.4577 allows remote authenticated users to hijack a valid web-management session. The web configuration constructs SESSION_ID as 2::2, exposing a small, time-derived token space instead of an unpredictable identifier. A valid session must exist, and successful timestamp brute forcing grants that session's management privileges and configuration capabilities.
The record
- CVE
- CVE-2021-46010
- Published
- Mar 30, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 30, 2022CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
- Predictable Session ID 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