openssl is vulnerable to Memory Leak
37
Low Risk
When OCSP response checking is enabled, a Basic OCSP response with an empty list of single responses returns early and skips freeing the OCSP_BASICRESP structure. A TLS server can repeat that response, and can pad it with extra certificates, so a long running client leaks memory on each handshake until it runs out of memory. The fix frees the response structure when the single response list is empty.
You are affected if you are using a version that falls within the vulnerable range and your TLS client enables OCSP response checking.
openssl is vulnerable to Memory Leak in versions 3.6.0 - 3.6.3 and 4.0.0 - 4.0.1.
Upgrade the openssl library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.