Vulnerability	Vulnerable Version
M Missing Report of Error Condition Affected versions of this package are vulnerable to Missing Report of Error Condition causing server authentication failures to not be detected by clients, due to handshakes not aborting as expected when the `SSL_VERIFY_PEER` verification mode is set. An attacker could impersonate a legitimate server by performing a MitM attack on TLS and DTLS connections using Raw Public Keys (RPKs). Note: This is only exploitable if TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to `SSL_VERIFY_PEER`; Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling `SSL_get_verify_result()`. Those that do, and take appropriate action, are not affected. How to fix Missing Report of Error Condition? Upgrade `cryptography` to version 44.0.1 or higher.	[42.0.0,44.0.1)
H Type Confusion Affected versions of this package are vulnerable to Type Confusion in the `do_x509_check()` function in `x509/v3_utl.c`, which is responsible for certificate name checks. An application that specifies an expected DNS name, Email address or IP address that performs a name check on an `otherName` subject alternative name of an X.509 certificate can be made to crash when it attempts to read an invalid memory address. Note: Users that are building cryptography source ("sdist") are responsible for upgrading their copy of OpenSSL. How to fix Type Confusion? Upgrade `cryptography` to version 43.0.1 or higher.	[37.0.0,43.0.1)

Missing Report of Error Condition

Affected versions of this package are vulnerable to Missing Report of Error Condition causing server authentication failures to not be detected by clients, due to handshakes not aborting as expected when the SSL_VERIFY_PEER verification mode is set. An attacker could impersonate a legitimate server by performing a MitM attack on TLS and DTLS connections using Raw Public Keys (RPKs).

Note:

This is only exploitable if TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER;
Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(). Those that do, and take appropriate action, are not affected.

How to fix Missing Report of Error Condition?

Upgrade cryptography to version 44.0.1 or higher.

[42.0.0,44.0.1)

Type Confusion

Affected versions of this package are vulnerable to Type Confusion in the do_x509_check() function in x509/v3_utl.c, which is responsible for certificate name checks. An application that specifies an expected DNS name, Email address or IP address that performs a name check on an otherName subject alternative name of an X.509 certificate can be made to crash when it attempts to read an invalid memory address.

Note: Users that are building cryptography source ("sdist") are responsible for upgrading their copy of OpenSSL.

How to fix Type Confusion?

Upgrade cryptography to version 43.0.1 or higher.

[37.0.0,43.0.1)

Go back to all versions of this package