2 ms·
What's interesting to me is we've known about these class of API misdesign issues since gets(3)... sometimes convenient and ergonomic is really not the right wa
by baq 4y ago
What's interesting to me is we've known about these class of API misdesign issues since gets(3)... sometimes convenient and ergonomic is really not the right way to do it.
- matt123456789 4y agoBut the class here is DoS-able, not buffer overrun. The “fixed” version of gets takes a max string length. This DoS-able function already does that. The concern here is different in that the library’s design encourages using untrusted input (Content-Length) to set the buffer size.