replay-attack · shipping

Replay attack

A replay attack reuses previously valid data to induce acceptance in an unauthorized context.

Related Observatory article: Replay attack on hesela.com

RFC 4949 describes replay for valid transmissions; the storage counterpart can restore an older authenticated block without forging its tag. Broz and colleagues explicitly exclude this threat from their 2018 sector-encryption design. [1] [2] Legitimate journal replay during crash recovery is not, by itself, an attack. [3]

Relations

related

rollback-protection, authenticated-encryption, cryptographic-nonce, dm-integrity

Citations

1. RFC 4949: Internet Security Glossary, Version 2 (2007), replay attack; informational glossary, not an Internet Standard (accessed 2026-10-15)
2. Broz, Patocka and Matyas: Practical cryptographic data integrity protection with full disk encryption (extended version), 2018, section 2.4 (accessed 2026-10-15)
3. Hesela: A trusted root still needs a version policy (accessed 2026-10-15)

JSON: /data/terms/replay-attack.json