Network attacks
Replay attack
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.
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.
Read next
- Man in the middle A machine placed on the path between two parties, able to read and alter what is not protected end to end.
- TLS and certificates Encryption plus proof of identity: the server shows a certificate for the name, signed by a trusted authority.
- Session hijacking Stealing a live session's identifier — a cookie read off the wire — and presenting it to the server to act as that user, without ever knowing their password.