Certified Ethical Hacker (CEH) Practice Question

During a gray-box assessment you notice the target web application propagates its session identifier as a long Base64 token appended to the query string of every internal hyperlink (for example, /dashboard?sid=eyJhbGciOi…). From a web application security perspective, what is the primary risk introduced by carrying authentication data in the URL instead of in an HttpOnly cookie?

  • JavaScript running in the same origin cannot read the token, preventing the application from implementing effective CSRF defenses.

  • The session token may leak through browser history, server logs, and Referer headers, making it easy for attackers to steal and reuse it.

  • Browsers will refuse to transmit the token over HTTPS connections, so authenticated requests will fail when TLS is used.

  • Placing the token in the URL disables the browser's same-origin policy, allowing any external domain to issue privileged requests.

Certified Ethical Hacker (CEH)
Web Application Hacking
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot