Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by hot_gril on Tuesday September 26, 2023 @08:01PM
(#37667682)
Right, but I can trust a decent C developer to use it safely in the simple parts, especially with tooling like valgrind to detect obvious bugs. The only part where I'd say the usual "nobody is perfect" is in the hard parts.
[ Parent
| on HN ]
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by pornel on Tuesday September 26, 2023 @08:37PM
(#37668078)
There's 40 years history of trying, and it doesn't work.
These decent C programmers are like True Scotsmen. When top software companies keep getting pwned, even in their most security-sensitive projects, it's because they hire crap programmers.
Even basic boring C can be exploitable. Android was hit by an integer overflow in `malloc(items * size)` (stagefright). Mozilla's NSS had vulnerability due to a wrong buffer size, which fuzzing did not catch (BigSig).