More OpenSSL Memory Corruption
Posted on 2022-06-27: https://twitter.com/cstanley/status/1541507298404827137
From @cstanley:
OpenSSL version 3.0.4, released on June 21th 2022, is susceptible to remote memory corruption which can be triggered trivially by an attacker. BoringSSL, LibreSSL and the OpenSSL 1.1.1 branch are not affected.
https://guidovranken.com/2022/06/27/notes-on-openssl-remote-memory-corruption/
Which is a quote tweet of the original report by @GuidoVranken:
The fix for this introduced a (probably remote?) memory corruption bug in the latest OpenSSL release.
Which is yet another quote tweet of the original original report by the same guy:
x64 modular exponentiation bug in OpenSSL and BoringSSL introduced in 2013
https://boringssl-review.googlesource.com/c/boringssl/+/52825
So yeah this is an old bug. And also wow cryptography is already so hard, let alone using C correctly, time to switch to a memory-safe language already geez “oh but GC-ed languages can’t do Crypto because timing attacks and real-time and blah blah” ok first of all they can still allocate scratch buffers and second of all I AM SHILLING FOR RUST