CVE-2022-32221
CVE Details
Visit the official vulnerability details page for CVE-2022-32221 to learn more.
Initial Publication
01/14/2025
Last Update
02/21/2025
Third Party Dependency
curl
NIST CVE Summary
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.
CVE Severity
Our Official Summary
This is a critical vulnerability in libcurl versions 7.7 through 7.85.0, where reusing a handle for HTTP(S) transfers from a PUT to a POST request can lead to unintended data transmission or potential memory issues. This unexpected behavior can cause the application to: a) Send unintended or incorrect data. b) Potentially access freed memory, leading to undefined behavior or application crashes. This can be exploited by attackers to manipulate the data sent in HTTP requests, potentially leading to information disclosure or remote code execution, depending on the application's context and the nature of the data being handled.
The images where this vulnrability is have controls in place are not accessible outside the cluster. So the attacker needs to gain privileged access to the cluster to attempt this exploit. Also the containers do not allow execution of arbitrary code. Impact of this exploit is also low, since container reduces the attack surface.
Status
Ongoing
Affected Products & Versions
| Version | Palette Enterprise | Palette Enterprise Airgap | VerteX | VerteX Airgap |
|---|---|---|---|---|
| 4.5.20 | ⚠️ Impacted | ✅ No Impact | ✅ No Impact | ✅ No Impact |
| 4.5.15 | ⚠️ Impacted | ✅ No Impact | ✅ No Impact | ✅ No Impact |
Revision History
| Date | Revision |
|---|---|
| 02/21/2025 | Status changed from Open to Ongoing |
| 02/21/2025 | Official summary added |
| 01/20/2025 | Impacted versions changed from 4.5.15 to 4.5.15, 4.5.20 |