44.0.2
11 years ago
1 months ago
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.
Fix for freeVulnerability | Vulnerable Version |
---|---|
Affected versions of this package are vulnerable to Type Confusion in the Note: Users that are building cryptography source ("sdist") are responsible for upgrading their copy of OpenSSL. How to fix Type Confusion? Upgrade | [37.0.0,43.0.1) |
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption due to improper user input validation in the 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 How to fix Uncontrolled Resource Consumption? Upgrade | [0,42.0.8) |
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 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 Observable Timing Discrepancy. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data (Marvin). Note: This vulnerability exists due to an incomplete fix for CVE-2020-25659. How to fix Observable Timing Discrepancy? Upgrade | [,42.0.0) |
Affected versions of this package are vulnerable to NULL Pointer Dereference when loading PKCS7 certificates. An attacker can cause a Denial of Service (DoS) by attempting to deserialize a PKCS7 blob/certificate. Note: This is only exploitable if the How to fix NULL Pointer Dereference? Upgrade | [3.1,41.0.6) |
Affected versions of this package are vulnerable to Denial of Service (DoS) when the Note: This is only exploitable if the application uses these functions to generate or check an X9.42 DH key or parameters. Also, the OpenSSL How to fix Denial of Service (DoS)? Upgrade | [,42.0.0) |
Affected versions of this package are vulnerable to Missing Cryptographic Step when the Both truncations and overruns of the key and the IV will produce incorrect results and could, in some cases, trigger a memory exception. How to fix Missing Cryptographic Step? Upgrade | [,41.0.5) |
Affected versions of this package are vulnerable to Denial of Service (DoS). The POLY1305 MAC (message authentication code) implementation might corrupt the internal state of applications on the Windows 64 platform when running on newer X86_64 processors supporting AVX512-IFMA instructions. If an attacker can influence whether the POLY1305 MAC algorithm is used in an application, the application state might be corrupted with various application dependent consequences, the most likely of which being denial of service. The maintainers are currently not aware of any concrete application that would be affected by this issue. NOTES: This vulnerability is only exploitable on Windows. The FIPS provider is not affected by this issue. How to fix Denial of Service (DoS)? Upgrade | [2.5,41.0.4) |
Affected versions of this package are vulnerable to Denial of Service (DoS) when the Note: The OpenSSL SSL/TLS implementation and the OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. How to fix Denial of Service (DoS)? Upgrade | [0.8,41.0.3) |
Affected versions of this package are vulnerable to Denial of Service (DoS) in the When the key or parameters that are being checked contain an excessively large modulus value (the The OpenSSL NOTE: The OpenSSL SSL/TLS implementation is not affected by this issue. How to fix Denial of Service (DoS)? Upgrade | [0.8,41.0.3) |
Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity in the AES-SIV cipher implementation in Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be misled by removing, adding or reordering such empty entries as these are ignored by the OpenSSL implementation. NOTE: This issue does not affect non-empty associated data authentication and the maintainers are currently unaware of any applications that use empty associated data entries. How to fix Insufficient Verification of Data Authenticity? Upgrade | [0.8,41.0.3) |
Affected versions of this package are vulnerable to Improper Certificate Validation in the SSH certificate decoding process. An attacker can cause the application to accept unauthorized SSH certificates generated by Note: This is only exploitable if the attacker controls the SSH certificate generation process or can introduce crafted SSH certificates into the system. How to fix Improper Certificate Validation? Upgrade | [,41.0.2) |
Affected versions of this package are vulnerable to Denial of Service (DoS) when processing specially crafted ASN.1 objects identifiers.
Applications that use How to fix Denial of Service (DoS)? Upgrade | [,41.0.0) |
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a null pointer dereference in when signatures are being verified on PKCS7 signed or signedAndEnveloped data in NOTE: The TLS implementation in OpenSSL does not call these functions. How to fix Denial of Service (DoS)? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a null dereference when validating DSA public keys in the NOTE: The TLS implementation in OpenSSL does not call this function. How to fix Denial of Service (DoS)? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Use After Free in the How to fix Use After Free? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') in How to fix Access of Resource Using Incompatible Type ('Type Confusion')? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Timing Attack in How to fix Timing Attack? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Denial of Service (DoS) due to an invalid pointer dereference in the NOTE: The TLS implementation in OpenSSL does not call these functions. How to fix Denial of Service (DoS)? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a read buffer overflow in certificate name constraint checking in How to fix Denial of Service (DoS)? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a double free after calling the How to fix Denial of Service (DoS)? Upgrade | [,39.0.1) |
Affected versions of this package are vulnerable to Expected Behavior Violation in How to fix Expected Behavior Violation? Upgrade | [1.8,39.0.1) |
Affected versions of this package are vulnerable to Denial of Service (DoS). If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows), this results in a denial of service when the affected process hangs. NOTE: Policy processing being enabled on a publicly-facing server is not considered to be a common setup. How to fix Denial of Service (DoS)? Upgrade | [0,39.0.1) |
Affected versions of this package are vulnerable to Buffer Overflow. A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow an arbitrary number of bytes containing the A full break down of this vulnerability can be found in our technical deep dive. NOTE: The Node.js project has announced that 18.x and 19.x releases are affected, and fixed versions are expected on or soon after November 3. This advisory will be updated accordingly when they are released. ChangelogNovember 1, 2022 - Advisory published. November 2, 2022 - Node.js listed as affected, in advance of fix. November 5, 2022 - Node.js fixed versions added. How to fix Buffer Overflow? Upgrade | [35.0.0,38.0.3) |
Affected versions of this package are vulnerable to Buffer Overflow. A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking by the Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. A full break down of this vulnerability can be found in our technical deep dive. Note: Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. ChangelogNovember 1, 2022 - Advisory published. November 2, 2022 - Node.js listed as affected, in advance of fix. November 5, 2022 - Node.js fixed versions added. How to fix Buffer Overflow? Upgrade | [35.0.0,38.0.3) |