VulnerableCode Package Details - pkg:cargo/openssl-src@111.23.0%2B1.1.1r

Search for packages

Vulnerability	Summary	Fixed by
VCID-9wtx-9sbn-aaam Aliases: CVE-2023-0286 GHSA-x4qr-2fvf-3mr5	Vulnerable OpenSSL included in cryptography wheels	111.25.0 Affected by 0 other vulnerabilities. 111.25.0+1.1.1t Affected by 0 other vulnerabilities. 300.0.12 Affected by 0 other vulnerabilities. 300.0.12+3.0.8 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.	111.25.0 Affected by 0 other vulnerabilities. 111.25.0+1.1.1t Affected by 0 other vulnerabilities. 300.0.12 Affected by 0 other vulnerabilities. 300.0.12+3.0.8 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.	111.25.0 Affected by 0 other vulnerabilities. 111.25.0+1.1.1t Affected by 0 other vulnerabilities. 300.0.12 Affected by 0 other vulnerabilities. 300.0.12+3.0.8 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.	111.25.0 Affected by 0 other vulnerabilities. 111.25.0+1.1.1t Affected by 0 other vulnerabilities. 300.0.12 Affected by 0 other vulnerabilities. 300.0.12+3.0.8 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-9wtx-9sbn-aaam
Aliases:
CVE-2023-0286
GHSA-x4qr-2fvf-3mr5

Vulnerable OpenSSL included in cryptography wheels

111.25.0
Affected by 0 other vulnerabilities.

111.25.0+1.1.1t
Affected by 0 other vulnerabilities.

300.0.12
Affected by 0 other vulnerabilities.

300.0.12+3.0.8
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.

111.25.0
Affected by 0 other vulnerabilities.

111.25.0+1.1.1t
Affected by 0 other vulnerabilities.

300.0.12
Affected by 0 other vulnerabilities.

300.0.12+3.0.8
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.

111.25.0
Affected by 0 other vulnerabilities.

111.25.0+1.1.1t
Affected by 0 other vulnerabilities.

300.0.12
Affected by 0 other vulnerabilities.

300.0.12+3.0.8
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.

111.25.0
Affected by 0 other vulnerabilities.

111.25.0+1.1.1t
Affected by 0 other vulnerabilities.

300.0.12
Affected by 0 other vulnerabilities.

300.0.12+3.0.8
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2024-10-07T21:05:19.113440+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.043790+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.547135+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.272767+00:00	GHSA Importer	Affected by	VCID-ur7f-5ey8-aaak	https://github.com/advisories/GHSA-p52g-cm5j-mjv4	34.0.2
2024-09-22T21:35:17.510613+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.594939+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.849658+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.544307+00:00	GHSA Importer	Affected by	VCID-ur7f-5ey8-aaak	https://github.com/advisories/GHSA-p52g-cm5j-mjv4	34.0.1