4 ms·
Lots: https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-767/GNU-Glibc.html https://www.cvedetails.com/vulnerability-list/vendor_id-72/p...
by rwmj 9y ago
Lots: https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-767/GNU-Glibc.html https://www.cvedetails.com/vulnerability-list/vendor_id-72/p...
- sebcat 9y agomusl: https://www.cvedetails.com/vulnerability-list/vendor_id-16859/Musl-libc.html https://www.cvedetails.com/vulnerability-list/vendor_id-1685... Can't find separate listings for libc in FreeBSD, OpenBSD but the list is smaller than glibc if you check e.g., VuXML or https://www.cvedetails.com/vulnerability-list/vendor_id-97/product_id-163/Openbsd-Openbsd.html https://www.cvedetails.com/vulnerability-list/vendor_id-97/p... Looks like glibc is the worst sinner here.
- rwmj 9y agoMore people study and use glibc, so I guess they find more bugs. On the other hand glibc has a larger code base. Anyway it's difficult to compare bug counts across projects.
- zuzun 9y agoHalf of them are logic errors and around 15 bugs are integer overflows of which the project above is riddled with.
- archi42 9y agoNo no, these are not bugs, you are just misinterpreting the {standard, API, intention, stars} ;-) /sarcasm
- archi42 9y agoHm, at those who downvoted me: Read some older glibc bug reports. For example the one about sscanf("foo", "%10s", strptr) returning 1. Hint: According to the standard, it should return 0. Musl does it right, which recently broke some of my test cases. But the bug is known and not fixed since years, maybe a decade...