cryptography@42.0.0 vulnerabilities
cryptography is a package which provides cryptographic recipes and primitives to Python developers.
-
latest version
42.0.6
-
latest non vulnerable version
-
first published
10 years ago
-
latest version published
a day ago
-
licenses detected
- [41.0.0,)
Direct Vulnerabilities
Known vulnerabilities in the cryptography package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
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 Note: This issue is only exploitable if the server supports TLSv1.3 and is configured with the How to fix Uncontrolled Resource Consumption ('Resource Exhaustion')? Upgrade |
[35.0.0,42.0.6)
|
Affected versions of this package are vulnerable to NULL Pointer Dereference in the Note: This is only exploitable if the vulnerable function is called with both:
How to fix NULL Pointer Dereference? Upgrade |
[38.0.0,42.0.4)
|
Affected versions of this package are vulnerable to NULL Pointer Dereference when processing a maliciously formatted PKCS12 file. The vulnerability exists due to improper handling of optional How to fix NULL Pointer Dereference? Upgrade |
[,42.0.2)
|
Affected versions of this package are vulnerable to Resource Exhaustion via the How to fix Resource Exhaustion? Upgrade |
[35.0.0,42.0.2)
|
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm due to an issue in the Note: This is only exploitable if the attacker has the ability to affect the algorithm's usage and the application relies on non-volatile XMM registers. How to fix Use of a Broken or Risky Cryptographic Algorithm? Upgrade |
[35.0.0,42.0.2)
|