Curl is C
I have no problem with Curl being written in C (I'll take battle-tested C over experimental Rust) but this point seemed odd to me:>C is not the primary reason for our past vulnerabilities>There. The simple fact is that most of our past vulnerabilities happened because of logical mistakes in the code. Logical mistakes that aren’t really language bound and they would not be fixed simply by changing language.So I looked at https://curl.haxx.se/docs/security.html#61 -> uninitialized random : libcurl's (new) internal function that returns a good 32bit random value was implemented poorly and overwrote the pointer instead of writing the value into the buffer the pointer pointed to.#60 -> printf floating point buffer overflow#57 -> cookie injection for other servers : The issue pertains to the function that loads cookies into memory, which reads the specified file into a fixed-size buffer in a line-by-line manner using the fgets() function. If an invocation of fgets() cannot read the whole line into the destination buffer due to it being too small, it truncates the outputThis one is arguably not really a failure of C itself, but I'd argue that Rust encourages a more robust error handling through its Options and Results when C tends to abuse "-1" and NULL return types that need careful checking and can't usually be enforced by the compiler.#55 -> OOB write via unchecked multiplicationRust has checked multiplication enabled by default in debug builds, and regardless of that the OOB wouldn't be possible.#54 -> Double free in curl_maprintf#53 -> Double free in krb5 code#52 -> glob parser write/read out of boundAnd I'll stop here, so far 7 out of 11 vulnerabilities would probably have been avoided with a safer language. Looks like the vast majority of these issues wouldn't have been possible in safe Rust.