Which of the following are common session management vulnerabilities? (Choose two)

Question

Options

• ASession IDs stored in URLs
• BRandom session ID generation
• CLack of session timeout policies
• DUse of encrypted session cookies

• A
  75% (38)
• B
  20% (10)
• D
  6% (3)

Explanation

Storing session IDs in URLs (A) is a well-known vulnerability because they appear in browser history, server logs, and referrer headers, making them trivial for attackers to steal - this is why modern frameworks use cookies instead. Lack of session timeout policies (C) is dangerous because indefinitely valid sessions give attackers an unlimited window to hijack them after obtaining a token through any means.

Why the distractors are wrong:

• B (Random session ID generation) is actually a best practice, not a vulnerability - unpredictable IDs prevent brute-force and guessing attacks.
• D (Encrypted session cookies) is also a best practice - encryption protects the cookie's contents from tampering and disclosure.

Memory tip: Think of vulnerabilities as things that make sessions easier to steal or reuse - URLs expose tokens publicly (bad), and no timeout means stolen tokens never expire (bad). Random generation and encryption both harden sessions, so they're defenses, not weaknesses.

No community discussion yet for this question.