AI analysis
Toptech TMS7 and TopHAT accept a session identifier supplied by the user and do not issue a new session ID after successful authentication, which is a session-fixation flaw (CWE-384). An attacker who can cause a victim to authenticate under a prechosen session ID can then reuse that same identifier and take over the authenticated session. Successful takeover can expose and modify data available to the victim's account, with limited availability impact. The issue affects deployments of these terminal-management products; exact version ranges were not stated in the advisory data. It is not listed in CISA KEV, and no public proof-of-concept is known.
What to do: Apply the vendor's security update for TMS7 and TopHAT as soon as it is available, and until then reject client-supplied session identifiers and force a new session ID immediately after authentication. Review authentication logs for sessions that were created before login and later reused by a different client, and restrict management interfaces to trusted networks.
Affected
| Toptech TMS7 | — |
| Toptech TopHAT | — |
Estimated exposure
nicheNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
The application accepts user-supplied session identifiers and does not regenerate the session ID after authentication. This allows an attacker to predefine a session ID and reuse it after victim authentication, resulting in session takeover.