← Back to Attack / Defense Lab
OSI LAYER 5 // Session Layer

Replay Attack

A replay attack reuses a previously captured valid message, token, or transaction in a context where freshness should have been required.

01 // HOW IT WORKS

Mechanism

The attacker does not need to understand or alter the original message if the protocol accepts it again without adequate freshness or uniqueness checks.

02 // DETECTION

Indicators to watch

Duplicate transaction identifiers, repeated nonces/timestamps, repeated authentication assertions, or identical requests outside expected timing windows.

03 // ATTACK FLOW

Concept diagram

01Valid message↓
02Captured token / transaction↓
03Message reused later↓
04Duplicate action↓
05Nonce + freshness checks
04 // PREVENTION

Defensive controls

Use nonces, timestamps, sequence numbers, short token lifetimes, challenge-response protocols, and server-side replay detection.

05 // SECURITY TOOL

Recommended security control

SIEM correlation + protocol logging

Use synthetic messages and timestamps in a closed lab.

06 // DEFENCE PRACTICE LAB

Defence practice lab

The administrator has not attached a tool link yet. This slot will show “Build Soon” until an external link is configured.

Build Soon
◈
DEFENCE PRACTICE LAB // BUILD SOONThe administrator can add or edit an external defence practice lab link from the private admin portal.
07 // DEFENCE TECHNIQUES

Defence techniques

Defence techniques for this attack will be added by the administrator.

AUTHORIZED LEARNING

All attack descriptions are for defensive education. Test scanning, traffic generation, interception, wireless testing, and vulnerable applications only on systems and networks you own or are explicitly authorized to assess.