GET /disp_reports.php?SectionEntered=57&GroupEntered=- 1&report_type=alerts&to_date=01-01- 0101&Run= Run&UserEntered=dsmith&SessionID=5f04189bc&from_date=31-10- 2010&TypesEntered=1 HTTP/1.1 Host…

Question

Options

• AThe HTTPS is not being enforced so the system is vulnerable.
• BThe numerical encoding on the session ID is limited to hexadecimal characters, making it susceptible
• CSensitive data is transmitted in the URL.
• DThe dates entered are outside a normal range, which may leave the system vulnerable to a denial

• A
  7% (3)
• B
  9% (4)
• C
  81% (35)
• D
  2% (1)

Explanation

The greatest concern is that sensitive data - specifically the SessionID and UserEntered (username) values - are transmitted in the URL as query string parameters (C). GET request URLs are logged in web server access logs, proxy logs, browser history, and can leak via HTTP Referer headers to third-party sites. A SessionID in a URL is particularly dangerous because any party with access to those logs can hijack the session. While HTTPS enforcement (A) is a valid concern, it only addresses transmission confidentiality and would not protect against log exposure of URL parameters. The hexadecimal session ID entropy (B) is a secondary concern. The out-of-range date (D) could suggest a SQL injection or DoS attempt but is less immediately impactful than the direct exposure of active session credentials in a loggable URL.

No community discussion yet for this question.