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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3288-1 | curl security update |
Debian DSA |
DSA-5330-1 | curl security update |
Ubuntu USN |
USN-5702-1 | curl vulnerabilities |
Ubuntu USN |
USN-5702-2 | curl vulnerability |
Ubuntu USN |
USN-5823-1 | MySQL vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-08-03T07:32:56.010Z
Reserved: 2022-06-01T00:00:00
Link: CVE-2022-32221
No data.
Status : Modified
Published: 2022-12-05T22:15:10.343
Modified: 2024-11-21T07:05:57.177
Link: CVE-2022-32221
OpenCVE Enrichment
No data.
Debian DLA
Debian DSA
Ubuntu USN