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.
Score:
cve_id status cvss3Score av ac pr ui ai
CVE-2022-32221 fixed 9.8 N L N N H
CVE-2022-32221: https:/ /nvd.nist. gov/vuln/ detail/ CVE-2022- 32221
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.
Score:
cve_id status cvss3Score av ac pr ui ai
CVE-2022-32221 fixed 9.8 N L N N H
References: 7.74.0- 1.3+deb11u3_ amd64.deb= ==>curl_ 7.74.0- 1.3+deb11u5_ amd64.deb' , 'libcurl3- gnutls_ 7.74.0- 1.3+deb11u3_ amd64.deb= ==>libcurl3- gnutls_ 7.74.0- 1.3+deb11u5_ amd64.deb' , 'libcurl4_ 7.74.0- 1.3+deb11u3_ amd64.deb= ==>libcurl4_ 7.74.0- 1.3+deb11u5_ amd64.deb' , 'libcurl4- gnutls- dev_7.74. 0-1.3+deb11u3_ amd64.deb= ==>libcurl4- gnutls- dev_7.74. 0-1.3+deb11u5_ amd64.deb' , 'libcurl4- openssl- dev_7.74. 0-1.3+deb11u3_ amd64.deb= ==>libcurl4- openssl- dev_7.74. 0-1.3+deb11u5_ amd64.deb' ]
['curl_