184 vulnerabilities classified as CWE-384 (会话固定). AI Chinese analysis included.
CWE-384, Session Fixation, is an authentication weakness where an application fails to invalidate existing session identifiers upon user login. This flaw allows attackers to predict or fix a victim’s session ID before authentication occurs. Typically, an attacker tricks a user into accessing a malicious link containing the attacker’s known session ID. When the victim logs in, the server associates the authenticated session with that pre-existing ID, granting the attacker immediate access to the victim’s account without needing credentials. To prevent this, developers must generate a new, random session identifier immediately after successful authentication. Additionally, implementing secure session management practices, such as regenerating IDs after privilege changes and using secure, HTTP-only cookies, ensures that stolen session tokens remain useless to attackers, effectively mitigating the risk of session hijacking.
private void auth(LoginContext lc, HttpSession session) throws LoginException { ... lc.login(); ... }<form method="POST" action="j_security_check"> <input type="text" name="j_username"> <input type="text" name="j_password"> </form>Vulnerabilities classified as CWE-384 (会话固定) represent 184 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.