CVE-2024-25977

The application does not change the session token when using the login or logout functionality. An attacker can set a session token in the victims browser (e.g. via XSS) and prompt the victim to log in (e.g. via a redirect to the login page). This results in the victims account being taken over.

Weakness

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

Extended Description

Such a scenario is commonly observed when:

Potential Mitigations

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/196.html
• https://cwe.mitre.org/data/definitions/21.html
• https://cwe.mitre.org/data/definitions/31.html
• https://cwe.mitre.org/data/definitions/39.html
• https://cwe.mitre.org/data/definitions/59.html
• https://cwe.mitre.org/data/definitions/60.html
• https://cwe.mitre.org/data/definitions/61.html

References

• http://seclists.org/fulldisclosure/2024/May/34
• https://github.com/HAWK-Digital-Environments/HAWKI/commit/146967f3148e92d1640ffebc21d8914e2d7fb3f1
• https://r.sec-consult.com/hawki
• http://seclists.org/fulldisclosure/2024/May/34
• https://github.com/HAWK-Digital-Environments/HAWKI/commit/146967f3148e92d1640ffebc21d8914e2d7fb3f1
• https://r.sec-consult.com/hawki