Google assigns a CVE for libwebp and gives it a 10.0 score
1–10 of 235 posts
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#2Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#3Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#4[flagged]
However we are going into the right direction.
Microsoft also has put this into place for all those codebases that aren't being rewritten any time soon,
https://learn.microsoft.com/en-us/cpp/code-quality/build-rel...
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#5[flagged]
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#6[flagged]
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#7[flagged]
Even if you can write secure code in unsafe languages, it’s still a problem. Bugs creep in over time as more people work on a project, changes are merged, it’s ported to other platforms, etc.
If your project has any longevity you can’t bet on your pristine C code staying pristine.
There are more safe languages than Rust though.
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#8[flagged]
Downvotes of course. Programmers like to think they can write secure code with no guardrails. The fact that CVE lists are full of memory errors in 2023 says otherwise. Even if you can write secure code in unsafe languages, it’s still a problem. Bugs creep in over time as more people work on a project, changes are merged, it’s ported to other platforms, etc. If your project has any longevity you can’t bet on your pris…
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#9[flagged]
Re: Google assigns a CVE for libwebp and gives it a 10.0 score
#10[flagged]