[1]: https://projectzero.google/2014/08/the-poisoned-nul-byte-201...
It's an evolution of the old "nop sled" idea from stack overflows (and viruses before that), where you don't know exactly what the stack addresses you're targeting are, but you can in your exploit trigger payload include data that will carpet bomb the stack with NOP instructions so that you have a big window to guess.
I would be curious to see how they were able to exploit it here.
Exploitation conditions are likely more challenging today but that’s the earliest reference I know for exploiting a single byte overflow.