Concepts / Network attacks

Network attacks

Replay attack

Also called replay, request replay, message replay, captured-request reuse

Resending a captured, still-valid request so the server honours it a second time — because nothing in the message ties it to a single use.

The same bytes, sent again
The same bytes, sent again

Nothing is cracked: a valid request is copied and resent. Unless the request carries a one-time nonce or a signed timestamp, the server cannot tell the copy from the original.

A replay attack resends a captured, still-valid request so the server acts on it again. Nothing is cracked: the attacker copies the bytes and sends them later. It works when the server ties no request to one use. The cure is freshness: a one-time nonce or a signed timestamp in the request, so a resend is refused as stale. An HMAC without one still replays. [[tls|TLS]] denies the cleartext capture.

See it on real machines

Read next

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab