Question 335 of 1,152
Threats, Vulnerabilities, and MitigationsmediumMultiple ChoiceObjective-mapped

SY0-701 Threats, Vulnerabilities, and Mitigations Practice Question

This SY0-701 practice question tests your understanding of threats, vulnerabilities, and mitigations. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A security analyst is reviewing the session management implementation of a web application. The application generates session tokens by computing the MD5 hash of the concatenation of the username and the current server timestamp rounded to the nearest hour. An attacker has obtained a valid session token for her own account and discovers that she can forge tokens for other users by simply substituting the username in the hash calculation with a known target username. Which type of attack is the web application most vulnerable to?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Session prediction

The session token is generated using MD5(username + timestamp rounded to the nearest hour). Since the attacker knows her own token and can compute the hash for any username with the same timestamp, she can predict tokens for other users. This is a classic session prediction vulnerability, as the token generation lacks sufficient entropy and relies on predictable inputs.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Session hijacking via cross-site scripting (XSS)

    Why it's wrong here

    Session hijacking via XSS requires an attacker to inject malicious script that steals the victim's session token. This scenario does not involve injecting script; it involves predicting the token without stealing it.

    When this WOULD be correct

    A web application stores session tokens in cookies without HttpOnly or Secure flags, and an attacker exploits an XSS vulnerability to steal a victim's cookie and impersonate them. The question would describe a stored/reflected XSS that allows cookie theft.

  • Session replay attack

    Why it's wrong here

    A session replay attack involves capturing a valid token and reusing it later to impersonate the same user. The vulnerability described allows the attacker to create a token for a different user, not replay a captured one.

    When this WOULD be correct

    A session replay attack would be correct if the question described an attacker intercepting a valid session token (e.g., via network sniffing) and reusing it to gain unauthorized access, without needing to modify the token or understand its generation method.

  • Session prediction

    Why this is correct

    The session token is generated using the username and a timestamp with low granularity, making it possible for an attacker who knows the algorithm to calculate valid tokens for any user. This is a classic session prediction vulnerability.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Session fixation

    Why it's wrong here

    Session fixation occurs when an attacker forces a victim to use a session token that the attacker knows. Here, the attacker is able to compute a token for the victim without any interaction, so it is prediction, not fixation.

    When this WOULD be correct

    A web application accepts session tokens from URL parameters and does not regenerate the token after login. An attacker sends a victim a link with a predefined session ID, and after the victim logs in, the attacker uses that same session ID to hijack the session.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SY0-701 exam frequently reuses these exact scenarios with slightly different constraints.

Session predictionCorrect answer

Why this is correct

The session token is generated using the username and a timestamp with low granularity, making it possible for an attacker who knows the algorithm to calculate valid tokens for any user. This is a classic session prediction vulnerability.

Session hijacking via cross-site scripting (XSS)Wrong answer — click to see why

Why this is wrong here

The vulnerability is in the predictable token generation (MD5 of username + timestamp), not in stealing tokens via XSS. The attacker forges tokens without needing to inject scripts or steal cookies.

★ When this WOULD be the correct answer

A web application stores session tokens in cookies without HttpOnly or Secure flags, and an attacker exploits an XSS vulnerability to steal a victim's cookie and impersonate them. The question would describe a stored/reflected XSS that allows cookie theft.

Why candidates choose this

Candidates may confuse any session-related attack with session hijacking, and XSS is a common vector for stealing tokens, but here the token is forged, not stolen.

Session replay attackWrong answer — click to see why

Why this is wrong here

A session replay attack involves capturing a valid session token and reusing it later to impersonate a user. In this scenario, the attacker is forging tokens for other users by manipulating the token generation algorithm, not replaying a captured token.

★ When this WOULD be the correct answer

A session replay attack would be correct if the question described an attacker intercepting a valid session token (e.g., via network sniffing) and reusing it to gain unauthorized access, without needing to modify the token or understand its generation method.

Why candidates choose this

Candidates may confuse 'replay' with any attack that involves using a token obtained from one session in another, overlooking that replay specifically requires capturing and reusing an existing token without alteration.

Session fixationWrong answer — click to see why

Why this is wrong here

Session fixation requires an attacker to force a victim to use a known session ID, but here the attacker can compute valid tokens for any user without needing to fixate a session ID.

★ When this WOULD be the correct answer

A web application accepts session tokens from URL parameters and does not regenerate the token after login. An attacker sends a victim a link with a predefined session ID, and after the victim logs in, the attacker uses that same session ID to hijack the session.

Why candidates choose this

Candidates may confuse the ability to forge tokens with the concept of fixing a session ID, as both involve an attacker controlling a session token, but the mechanisms differ.

Analysis generated from the official SY0-701blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is confusing session prediction with session hijacking via XSS or session replay, but the key clue is that the attacker can compute the token herself by substituting the username, which directly indicates a predictable token generation scheme.

Trap categories for this question

  • Scenario analysis trap

    Session hijacking via XSS requires an attacker to inject malicious script that steals the victim's session token. This scenario does not involve injecting script; it involves predicting the token without stealing it.

Detailed technical explanation

How to think about this question

MD5 is a 128-bit cryptographic hash function that is no longer considered secure for session management due to its speed and collision vulnerabilities. Rounding the timestamp to the nearest hour reduces the keyspace to at most 24 possible values per day, making brute-force or prediction trivial. In practice, secure session tokens should use a cryptographically random number generator (CSPRNG) with at least 128 bits of entropy, as recommended by RFC 6269 and OWASP guidelines.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SY0-701 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Threats, Vulnerabilities, and Mitigations — This question tests Threats, Vulnerabilities, and Mitigations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Session prediction — The session token is generated using MD5(username + timestamp rounded to the nearest hour). Since the attacker knows her own token and can compute the hash for any username with the same timestamp, she can predict tokens for other users. This is a classic session prediction vulnerability, as the token generation lacks sufficient entropy and relies on predictable inputs.

What should I do if I get this SY0-701 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SY0-701 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.