cryptography 42.0.5 vulnerabilities

Known vulnerabilities in the cryptography package. This does not include vulnerabilities belonging to this package’s dependencies.

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)
L Uncontrolled Resource Consumption Affected versions of this package are vulnerable to Uncontrolled Resource Consumption due to improper user input validation in the `EVP_PKEY_param_check` or `EVP_PKEY_public_check` functions. An attacker can cause a denial of service by supplying excessively long DSA keys or parameters obtained from an untrusted source. Note: OpenSSL does not call these functions on untrusted DSA keys, so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL `pkey` and `pkeyparam` command line applications when using the "-check" option. How to fix Uncontrolled Resource Consumption? Upgrade `cryptography` to version 42.0.8 or higher.	[0,42.0.8)
L Uncontrolled Resource Consumption ('Resource Exhaustion') Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the session cache entering an incorrect state and failing to flush properly as it fills, leading to uncontrolled memory consumption. This condition is triggered under certain server configurations when processing TLSv1.3 sessions. Specifically, this occurs if the non-default `SSL_OP_NO_TICKET` option is enabled, but not if early_data support is configured along with the default anti-replay protection. A malicious client could deliberately create this scenario to force a service disruption. It may also occur accidentally in normal operation. Note: This issue is only exploitable if the server supports TLSv1.3 and is configured with the `SSL_OP_NO_TICKET` option enabled. How to fix Uncontrolled Resource Consumption ('Resource Exhaustion')? Upgrade `cryptography` to version 42.0.6 or higher.	[35.0.0,42.0.6)

Vulnerability

Vulnerable Version

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)

Uncontrolled Resource Consumption

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption due to improper user input validation in the EVP_PKEY_param_check or EVP_PKEY_public_check functions. An attacker can cause a denial of service by supplying excessively long DSA keys or parameters obtained from an untrusted source.

Note:

OpenSSL does not call these functions on untrusted DSA keys, so only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the "-check" option.

How to fix Uncontrolled Resource Consumption?

Upgrade cryptography to version 42.0.8 or higher.

[0,42.0.8)

Uncontrolled Resource Consumption ('Resource Exhaustion')

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the session cache entering an incorrect state and failing to flush properly as it fills, leading to uncontrolled memory consumption. This condition is triggered under certain server configurations when processing TLSv1.3 sessions. Specifically, this occurs if the non-default SSL_OP_NO_TICKET option is enabled, but not if early_data support is configured along with the default anti-replay protection. A malicious client could deliberately create this scenario to force a service disruption. It may also occur accidentally in normal operation.

Note:

This issue is only exploitable if the server supports TLSv1.3 and is configured with the SSL_OP_NO_TICKET option enabled.

How to fix Uncontrolled Resource Consumption ('Resource Exhaustion')?

Upgrade cryptography to version 42.0.6 or higher.

[35.0.0,42.0.6)

cryptography@42.0.5 vulnerabilities

cryptography is a package which provides cryptographic recipes and primitives to Python developers.

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?