Search for packages
| purl | pkg:ebuild/dev-libs/openssl@1.1.1q |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1mkj-94qc-zqgn | Buffer Overflow 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 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. |
CVE-2021-3711
GHSA-5ww6-px42-wc85 |
| VCID-aa9w-ntqw-pfbt | Multiple vulnerabilities have been discovered in OpenSSL, the worst of which could result in denial of service. |
CVE-2020-1968
|
| VCID-frd6-gt2a-afhv | Multiple vulnerabilities have been discovered in OpenSSL, the worst of which could result in denial of service. |
CVE-2022-2097
GHSA-3wx7-46ch-7rq2 |
| VCID-gsbn-6t86-7kf9 | Loop with Unreachable Exit Condition ('Infinite Loop') 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 |
CVE-2022-0778
GHSA-x3mh-jvjw-3xwx |
| VCID-myuq-u3as-g3ah | Carry Propagation bug There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. |
CVE-2021-4160
|
| VCID-nr5y-ve9m-zfeh | Out-of-bounds Read 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 |
| VCID-q2ae-5r8q-3fbv | Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') The `c_rehash` script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the `c_rehash` script is considered obsolete and should be replaced by the OpenSSL `rehash` command line tool. |
CVE-2022-1292
|
| VCID-zhwv-pq2x-8bey | Improper Resource Shutdown or Release The `OPENSSL_LH_flush()` function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time. Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. |
CVE-2022-1473
GHSA-g323-fr93-4j3c |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2026-04-01T13:03:43.130502+00:00 | Gentoo Importer | Fixing | VCID-frd6-gt2a-afhv | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.119666+00:00 | Gentoo Importer | Fixing | VCID-zhwv-pq2x-8bey | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.110273+00:00 | Gentoo Importer | Fixing | VCID-q2ae-5r8q-3fbv | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.100681+00:00 | Gentoo Importer | Fixing | VCID-gsbn-6t86-7kf9 | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.089835+00:00 | Gentoo Importer | Fixing | VCID-myuq-u3as-g3ah | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.080443+00:00 | Gentoo Importer | Fixing | VCID-nr5y-ve9m-zfeh | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.070843+00:00 | Gentoo Importer | Fixing | VCID-1mkj-94qc-zqgn | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |
| 2026-04-01T13:03:43.061673+00:00 | Gentoo Importer | Fixing | VCID-aa9w-ntqw-pfbt | https://security.gentoo.org/glsa/202210-02 | 38.0.0 |