CVE and update status of the FreeBSD ports tree4,526 unaddressed CVEs in 616 portsAll times are CET

CVE details

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
9.8 critical
Published
2022-12-05
Links
NVD · cve.org

Affected ports (2)

PortPackageVersionStatusMaintainer
ftp/linux-c7-curllinux-c7-curl7.29.0_13unaddressedemulation@FreeBSD.org
ftp/linux-rl9-curllinux-rl9-curl7.76.1_13unaddressedemulation@FreeBSD.org

VuXML

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>linux-c7-curl</name>
	<range><lt>7.86.0</lt></range>
      </package>
      <package>
	<name>linux-rl9-curl</name>
	<range><lt>7.86.0</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2022-32221</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2022-32221</url>
    </references>
    <dates>
      <discovery>2022-12-05</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>