Description
Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
Problem types
Product status
3.6.0 (semver) before 3.6.2
3.5.0 (semver) before 3.5.6
3.4.0 (semver) before 3.4.5
3.3.0 (semver) before 3.3.7
3.0.0 (semver) before 3.0.20
1.1.1 (custom) before 1.1.1zg
Credits
Igor Morgenstern (Aisle Research)
Viktor Dukhovni
Alexandr Nedvedicky
References
openssl-library.org/news/secadv/20260407.txt (OpenSSL Advisory)
github.com/...ommit/258a8f63b26995ba357f4326da00e19e29c6acbe (3.6.2 git commit)
github.com/...ommit/444958deaf450aea819171f97ae69eaedede42c3 (3.5.6 git commit)
github.com/...ommit/07e727d304746edb49a98ee8f6ab00256e1f012b (3.4.5 git commit)
github.com/...ommit/7a4e08cee62a728d32e60b0de89e6764339df0a7 (3.3.7 git commit)
github.com/...ommit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177 (3.0.20 git commit)