4 ms·
I think your wording is off, because 70% of reports bugs are not memory related. I vaguely recall that 70% of *certain classes* of reported security flaws were
by wredue 3y ago
I think your wording is off, because 70% of reports bugs are not memory related.
I vaguely recall that 70% of *certain classes* of reported security flaws were buffer misuses (which zig handles quite nicely in releasesafe and using slices, which is recommended)
Edit:
Found it:
70% of security bugs were counted as safe buffer related. Note that by sticking to slices and releaseSafe, zig provides most of the same guarantees as rust in this arena.
It’s unclear whether a buffer issue automatically classified a bug as a security flaw as well, as in many cases it’s simply not. For example, a memory security flaw was reported in Stockfish that was simply not a flaw.
We are also discussing the Microsoft OS, which is a whole different beast than applications.
Overall, meh.
- throwaway17_17 3y agoI probably should have substituted 70% with (some percentage big enough to attempt to draw conclusions). But I think I got the 70% from so ‘blank says 70% of exploits in our codebase are memory related’, but I could be mis-remembering. I tried to make it as broad and encompassing as I have seen the claim used in arguments for memory-safety-centric programming.
- kupfer 3y ago"70 percent of all security bugs are memory safety issues" (https://www.zdnet.com/article/microsoft-70-percent-of-all-security-bugs-are-memory-safety-issues/ https://www.zdnet.com/article/microsoft-70-percent-of-all-se...)