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

CVE details

CVE-2021-22926

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.

Score
7.5 high
Published
2021-08-05
Links
NVD · cve.org

Affected ports (1)

PortPackageVersionStatusMaintainer
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-rl9-curl</name>
	<range><lt>7.78.0</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2021-22926</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2021-22926</url>
    </references>
    <dates>
      <discovery>2021-08-05</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>