rustsec-2022-0059
Vulnerability from osv_rustsec
OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new()
function and associated function calls. This function was deprecated in OpenSSL
3.0 and application authors are instead encouraged to use the new provider
mechanism in order to implement custom ciphers.
OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed
to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2()
functions (as well as other similarly named encryption and decryption
initialisation functions). Instead of using the custom cipher directly it
incorrectly tries to fetch an equivalent cipher from the available providers.
An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new().
This NID is supposed to represent the unique NID for a given cipher. However it
is possible for an application to incorrectly pass NID_undef as this value in
the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the
OpenSSL encryption/decryption initialisation function will match the NULL cipher
as being equivalent and will fetch this from the available providers. This will
succeed if the default provider has been loaded (or if a third party provider
has been loaded that offers this cipher). Using the NULL cipher means that the
plaintext is emitted as the ciphertext.
Applications are only affected by this issue if they call EVP_CIPHER_meth_new()
using NID_undef and subsequently use it in a call to an encryption/decryption
initialisation function. Applications that only use SSL/TLS are not impacted by
this issue.
{
"affected": [
{
"database_specific": {
"categories": [
"crypto-failure"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "openssl-src",
"purl": "pkg:cargo/openssl-src"
},
"ranges": [
{
"events": [
{
"introduced": "300.0.0"
},
{
"fixed": "300.0.10"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2022-3358",
"GHSA-4f63-89w9-3jjv"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "OpenSSL supports creating a custom cipher via the legacy `EVP_CIPHER_meth_new()`\nfunction and associated function calls. This function was deprecated in OpenSSL\n3.0 and application authors are instead encouraged to use the new provider\nmechanism in order to implement custom ciphers.\n\nOpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed\nto the `EVP_EncryptInit_ex2()`, `EVP_DecryptInit_ex2()` and `EVP_CipherInit_ex2()`\nfunctions (as well as other similarly named encryption and decryption\ninitialisation functions). Instead of using the custom cipher directly it\nincorrectly tries to fetch an equivalent cipher from the available providers.\nAn equivalent cipher is found based on the NID passed to `EVP_CIPHER_meth_new()`.\nThis NID is supposed to represent the unique NID for a given cipher. However it\nis possible for an application to incorrectly pass `NID_undef` as this value in\nthe call to `EVP_CIPHER_meth_new()`. When `NID_undef` is used in this way the\nOpenSSL encryption/decryption initialisation function will match the NULL cipher\nas being equivalent and will fetch this from the available providers. This will\nsucceed if the default provider has been loaded (or if a third party provider\nhas been loaded that offers this cipher). Using the NULL cipher means that the\nplaintext is emitted as the ciphertext.\n\nApplications are only affected by this issue if they call `EVP_CIPHER_meth_new()`\nusing `NID_undef` and subsequently use it in a call to an encryption/decryption\ninitialisation function. Applications that only use SSL/TLS are not impacted by\nthis issue.",
"id": "RUSTSEC-2022-0059",
"modified": "2023-06-13T13:10:24Z",
"published": "2022-10-11T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/openssl-src"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0059.html"
},
{
"type": "WEB",
"url": "https://www.openssl.org/news/secadv/20221011.txt"
}
],
"related": [],
"severity": [],
"summary": "Using a Custom Cipher with `NID_undef` may lead to NULL encryption"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.