Two of the bugs AISLE highlighted are memory corruption primitives. They could be used in certain situations to crash a program that was running OpenSSL (like a web server), which is a denial of service risk. Because of modern compiler safety techniques, they can’t on their own be used to access data or run code, but they’re still concerning because it sometimes turns out to be possible to chain primitives like these into more dangerous exploits.
The third bug is a “timing side-channel bug” with a particular opt-in certificate algorithm that OpenSSL provides, when used on ARM architectures. It’s a pretty niche circumstance but it does look legitimate to me. The only way to know if it’s exploitable would be to try to build some kind of a PoC.
OpenSSL is a very hardened target, and lots of security researchers look at it. Any security-relevant bugs found on OpenSSL are pretty impressive.
Two of the bugs AISLE highlighted are memory corruption primitives. They could be used in certain situations to crash a program that was running OpenSSL (like a web server), which is a denial of service risk. Because of modern compiler safety techniques, they can’t on their own be used to access data or run code, but they’re still concerning because it sometimes turns out to be possible to chain primitives like these into more dangerous exploits.
The third bug is a “timing side-channel bug” with a particular opt-in certificate algorithm that OpenSSL provides, when used on ARM architectures. It’s a pretty niche circumstance but it does look legitimate to me. The only way to know if it’s exploitable would be to try to build some kind of a PoC.
OpenSSL is a very hardened target, and lots of security researchers look at it. Any security-relevant bugs found on OpenSSL are pretty impressive.