In a session hijacking test using Ettercap, which protocol is not inherently session-based, allowing hijacking?

In a session hijacking test using Ettercap, which protocol is not inherently session-based, allowing hijacking?

• A. FTP traffic can be hijacked
• B. HTTPS session can be hijacked
• C. HTTP protocol does not maintain session
• D. DNS traffic can be hijacked

Answer: (C)

HTTP is stateless by design; the protocol itself does not maintain a continuing session between client and server. In a session hijacking test with a tool like Ettercap, this means there isn’t an inherent, built‑in session state to seize at the protocol level. Attackers often rely on application‑level mechanisms like cookies or tokens to establish and manage a user session, and those can be stolen or replayed if not properly protected. Since HTTP does not enforce a persistent session through the protocol itself, it fits the idea that it isn’t inherently session‑based, making it the candidate described in the question. By contrast, protocols like FTP and HTTPS rely on actual session concepts: FTP maintains a session during a login and file transfer sequence, and HTTPS uses TLS to create and protect a secure session with keys for the duration of the connection. DNS operates differently and isn’t about long‑lived user sessions, so it isn’t described as inherently session‑based in the same context.

HTTP is stateless by design; the protocol itself does not maintain a continuing session between client and server. In a session hijacking test with a tool like Ettercap, this means there isn’t an inherent, built‑in session state to seize at the protocol level. Attackers often rely on application‑level mechanisms like cookies or tokens to establish and manage a user session, and those can be stolen or replayed if not properly protected. Since HTTP does not enforce a persistent session through the protocol itself, it fits the idea that it isn’t inherently session‑based, making it the candidate described in the question.

By contrast, protocols like FTP and HTTPS rely on actual session concepts: FTP maintains a session during a login and file transfer sequence, and HTTPS uses TLS to create and protect a secure session with keys for the duration of the connection. DNS operates differently and isn’t about long‑lived user sessions, so it isn’t described as inherently session‑based in the same context.