🚨 BREAKING: OPENSSL 4.1 CHANGED HOW TLS CERTIFICATES ARE VERIFIED, AND CURL STARTED ACCEPTING CERTIFICATES IT PREVIOUSLY REJECTED
Researchers showed curl 8.23.0 built against OpenSSL 4.1.0 accepts a certificate issued outside a CA's permitted DNS namespace. The same test fails on OpenSSL 4.0.2.
curl's verification code didn't change. OpenSSL dropped an old Common Name (CN) constraint check, and that left a gap between how the library validates the chain and how curl checks the hostname.
Daniel Stenberg, curl's creator, has publicly criticised the change. OpenSSL maintainers say the new behaviour follows the RFCs.
Exploiting it takes a trusted CA chain, a constrained intermediate certificate and curl's legacy hostname verification, so it's far from a universal TLS bypass. curl is working on removing its CN fallback.
Writeup, PoC and the OpenSSL vs curl argument: https://thecybersecguru.com/news/openssl-4-1-curl-name-constraints-bypass/