GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — CVE-2021-4044 - GitHub Advisory Database

Invalid handling of `X509_verify_cert()` internal errors in libssl

High severity GitHub Reviewed Published Dec 15, 2021 to the GitHub Advisory Database • Updated Nov 9, 2023

Package

openssl-src (Rust)

Affected versions

>= 300.0.0, < 300.0.4

Patched versions

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).

References

  • https://nvd.nist.gov/vuln/detail/CVE-2021-4044
  • https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=758754966791c537ea95241438454aa86f91f256
  • https://www.openssl.org/news/secadv/20211214.txt
  • https://rustsec.org/advisories/RUSTSEC-2021-0129.html
  • https://security.netapp.com/advisory/ntap-20211229-0003/
  • https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=758754966791c537ea95241438454aa86f91f256
Published by the National Vulnerability Database Dec 14, 2021
Published to the GitHub Advisory Database Dec 15, 2021
Reviewed Jun 17, 2022
Last updated Nov 9, 2023

Severity

High
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

(99th percentile)

Weaknesses

Weakness CWE-835

Loop with Unreachable Exit Condition

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Learn more on MITRE.

CVE ID

CVE-2021-4044

GHSA ID

GHSA-mmjf-f5jw-w72q

Source code

No known source code

Credits

  • @pinkforest pinkforest Analyst
Loading Checking history

Uh oh!

There was an error while loading. Please reload this page.

See something to contribute? Suggest improvements for this vulnerability.
You are visitor 01402639 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.