Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2021-4044

Published: 14 December 2021

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

Priority

Medium

Cvss 3 Severity Score

7.5

Score breakdown

Status

Package Release Status
openssl
Launchpad, Ubuntu, Debian
hirsute Not vulnerable
(code not present)
impish Not vulnerable
(code not present)
jammy
Released (3.0.1-0ubuntu1)
trusty Not vulnerable
(code not present)
upstream Not vulnerable
(debian: Vulnerable code not present)
xenial Not vulnerable
(code not present)
bionic Not vulnerable
(code not present)
focal Not vulnerable
(code not present)
openssl1.0
Launchpad, Ubuntu, Debian
bionic Not vulnerable
(code not present)
focal Does not exist

hirsute Does not exist

impish Does not exist

trusty Does not exist

upstream Needs triage

xenial Does not exist

jammy Does not exist

nodejs
Launchpad, Ubuntu, Debian
bionic Not vulnerable
(uses system openssl1.0)
focal Not vulnerable
(uses system openssl1.1)
hirsute Not vulnerable
(uses system openssl1.1)
trusty Not vulnerable
(uses system openssl)
xenial Not vulnerable
(uses system openssl)
impish Not vulnerable
(uses system openssl1.1)
upstream Needs triage

jammy Not vulnerable
(uses system openssl1.1)
edk2
Launchpad, Ubuntu, Debian
bionic Not vulnerable
(code not present)
focal Not vulnerable
(code not present)
hirsute Not vulnerable
(code not present)
impish Not vulnerable
(code not present)
trusty Does not exist

upstream Needs triage

xenial Not vulnerable
(code not present)
jammy Not vulnerable
(code not present)

Severity score breakdown

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