CVE-2021-22926
CVE Details
Visit the official vulnerability details page for CVE-2021-22926 to learn more.
Initial Publication
01/14/2025
Last Update
01/20/2025
Third Party Dependency
curl
NIST CVE Summary
libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the `CURLOPT_SSLCERT` option (`--cert` with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like `/tmp`), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.
CVE Severity
Our Official Summary
Curl libcurl could allow a remote attacker to bypass security restrictions, caused by a flaw in the CURLOPT_SSLCERT option mixup with TLS library Secure Transport. By creating a specially-crafted file name with the same name as the app wants to use by name, an attacker could exploit this vulnerability to trick the application to use the file based cert instead of the one referred to by name, and allow libcurl to send the wrong client certificate in the TLS connection handshake.
Containers where this vulnerabiity is repored, does not allow arbitrary code to execute, which is necessary to exploit this vulnerability. Hence the risk for our products is low. Impact of exploitation is also low as attack surface is limited to the container image.
Status
Ongoing
Affected Products & Versions
Version | Palette Enterprise | Palette Enterprise Airgap | VerteX | VerteX Airgap |
---|---|---|---|---|
4.5.20 | ⚠️ Impacted | ✅ No Impact | ⚠️ Impacted | ✅ No Impact |
4.5.15 | ⚠️ Impacted | ✅ No Impact | ⚠️ Impacted | ✅ No Impact |
Revision History
Date | Revision |
---|---|
01/20/2025 | Impacted versions changed from 4.5.15 to 4.5.15, 4.5.20 |
01/16/2025 | Status changed from Open to Ongoing |
01/16/2025 | Official summary added |