About this interactive
What you are doing: deciding whether each finding is a replay attack.
In a replay attack the attacker captures traffic, such as a login exchange, a session token or a request, and sends it again. The attacker does not need to read or change it. That is why hashing or encrypting a credential is not enough on its own: if the protocol accepts the same message twice, the captured copy works. Protocols stop replay with something that changes every time, such as a timestamp, a one-time value or a session that expires.
How to use it: ask whether captured traffic was sent again unchanged. Guessing, cracking, reading, altering and flooding are other attacks.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →