A four-byte write is a memory corruption primitive that overwrites exactly 4 bytes at a chosen address. That may sound small, but 4 bytes can still change an integer, pointer, flag, length field, or other control data that later influences program behavior. In exploit work, attackers value these “tiny” writes because they can redirect execution, weaken a check, or corrupt state without needing a large buffer overwrite.
In practice, a four-byte write often appears alongside another flaw, such as an out-of-bounds access, use-after-free, or timing bug. On modern systems, defenders look for it because even limited corruption can bypass assumptions in hardened code, especially inside security-sensitive components. Good defenses include memory-safe coding, bounds checks, pointer validation, and mitigations that make small overwrites less useful.