Search for packages
| purl | pkg:cargo/openssl-src@111.16.0%2B1.1.1l |
| Next non-vulnerable version | 111.25.0+1.1.1t |
| Latest non-vulnerable version | 300.0.12+3.0.8 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-5khv-27u8-aaaa
Aliases: CVE-2022-2097 GHSA-3wx7-46ch-7rq2 VC-OPENSSL-20220705-CVE-2022-2097 |
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). |
Affected by 0 other vulnerabilities. Affected by 4 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 12 other vulnerabilities. |
|
VCID-6pjh-cgdt-aaaj
Aliases: CVE-2022-0778 GHSA-x3mh-jvjw-3xwx VC-OPENSSL-20220315-CVE-2022-0778 |
The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). |
Affected by 0 other vulnerabilities. Affected by 17 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-9wtx-9sbn-aaam
Aliases: CVE-2023-0286 GHSA-x4qr-2fvf-3mr5 |
Vulnerable OpenSSL included in cryptography wheels |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-ec3y-aejm-aaad
Aliases: CVE-2022-4450 GHSA-v5w6-wcm8-jm4q |
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-ur7f-5ey8-aaak
Aliases: CVE-2022-4304 GHSA-p52g-cm5j-mjv4 |
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-uua4-ygek-aaah
Aliases: CVE-2023-0215 GHSA-r7jw-wp68-3xch |
The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-ghgs-7167-aaag | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y). |
CVE-2021-3712
GHSA-q9wj-f4qw-6vfj VC-OPENSSL-20210824-CVE-2021-3712 |
| VCID-r7qs-74zt-aaab | In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). |
CVE-2021-3711
GHSA-5ww6-px42-wc85 VC-OPENSSL-20210824-CVE-2021-3711 |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2024-10-07T21:05:19.079952+00:00 | GHSA Importer | Affected by | VCID-9wtx-9sbn-aaam | https://github.com/advisories/GHSA-x4qr-2fvf-3mr5 | 34.0.2 |
| 2024-10-07T21:05:15.010220+00:00 | GHSA Importer | Affected by | VCID-uua4-ygek-aaah | https://github.com/advisories/GHSA-r7jw-wp68-3xch | 34.0.2 |
| 2024-10-07T20:56:43.513794+00:00 | GHSA Importer | Affected by | VCID-ec3y-aejm-aaad | https://github.com/advisories/GHSA-v5w6-wcm8-jm4q | 34.0.2 |
| 2024-10-07T20:56:15.239047+00:00 | GHSA Importer | Affected by | VCID-ur7f-5ey8-aaak | https://github.com/advisories/GHSA-p52g-cm5j-mjv4 | 34.0.2 |
| 2024-10-07T20:04:40.074290+00:00 | GHSA Importer | Affected by | VCID-5khv-27u8-aaaa | https://github.com/advisories/GHSA-3wx7-46ch-7rq2 | 34.0.2 |
| 2024-10-07T19:55:57.052050+00:00 | GHSA Importer | Affected by | VCID-6pjh-cgdt-aaaj | https://github.com/advisories/GHSA-x3mh-jvjw-3xwx | 34.0.2 |
| 2024-10-07T19:35:35.604798+00:00 | GHSA Importer | Fixing | VCID-ghgs-7167-aaag | https://github.com/advisories/GHSA-q9wj-f4qw-6vfj | 34.0.2 |
| 2024-10-07T19:35:35.124086+00:00 | GHSA Importer | Fixing | VCID-r7qs-74zt-aaab | https://github.com/advisories/GHSA-5ww6-px42-wc85 | 34.0.2 |
| 2024-09-22T21:35:17.473392+00:00 | GHSA Importer | Affected by | VCID-9wtx-9sbn-aaam | https://github.com/advisories/GHSA-x4qr-2fvf-3mr5 | 34.0.1 |
| 2024-09-22T21:35:13.557776+00:00 | GHSA Importer | Affected by | VCID-uua4-ygek-aaah | https://github.com/advisories/GHSA-r7jw-wp68-3xch | 34.0.1 |
| 2024-09-22T21:33:52.811988+00:00 | GHSA Importer | Affected by | VCID-ec3y-aejm-aaad | https://github.com/advisories/GHSA-v5w6-wcm8-jm4q | 34.0.1 |
| 2024-09-22T21:33:25.505651+00:00 | GHSA Importer | Affected by | VCID-ur7f-5ey8-aaak | https://github.com/advisories/GHSA-p52g-cm5j-mjv4 | 34.0.1 |
| 2024-09-22T20:43:14.554048+00:00 | GHSA Importer | Affected by | VCID-5khv-27u8-aaaa | https://github.com/advisories/GHSA-3wx7-46ch-7rq2 | 34.0.1 |
| 2024-09-22T20:41:46.630527+00:00 | GHSA Importer | Affected by | VCID-6pjh-cgdt-aaaj | https://github.com/advisories/GHSA-x3mh-jvjw-3xwx | 34.0.1 |
| 2024-09-22T20:21:45.407894+00:00 | GHSA Importer | Fixing | VCID-ghgs-7167-aaag | https://github.com/advisories/GHSA-q9wj-f4qw-6vfj | 34.0.1 |
| 2024-09-22T20:21:44.829023+00:00 | GHSA Importer | Fixing | VCID-r7qs-74zt-aaab | https://github.com/advisories/GHSA-5ww6-px42-wc85 | 34.0.1 |