3 ms·
> Number one was Out-of-bounds Write (CWE-787) Surely many of these originate from deserialization of untrusted data (e.g., trusting a supplied length). It’s p
by stouset 2y ago
> Number one was Out-of-bounds Write (CWE-787)
Surely many of these originate from deserialization of untrusted data (e.g., trusting a supplied length). It’s probably documented but I’m passively curious how they disambiguate these cases.
- throw0101d 2y ago>> Number one was Out-of-bounds Write (CWE-787) > Surely many of these originate from deserialization of untrusted data (e.g., trusting a supplied length). Then they would presumably be classified under "Deserialization of Untrusted Data", number fifteen.
- stouset 2y agoThat’s entirely my point. If a vulnerability happens due to writing out of bounds during untrusted deserialization, which category would you file it under? “Deserialization of untrusted data” isn’t even a security bug like an out of bounds write is. Every meaningful program deserializes external input. It’s a common area where bugs occur, but it’s not a type of bug in and of itself. Every bug in that category “belongs” in a more proximate category.