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

CVE details

CVE-2023-40217

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Score
5.3 medium
Published
2023-08-25
Links
NVD · cve.org

Affected ports (1)

PortPackageVersionStatusMaintainer
lang/python27python272.7.18_5unaddressedpython@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>python27</name>
	<range><lt>3.8.18</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18,
	3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects
	servers (such as HTTP servers) that use TLS client authentication. If
	a TLS server-side socket is created, receives data into the socket
	buffer, and then is closed quickly, there is a brief window where the
	SSLSocket instance will detect the socket as "not connected" and won't
	initiate a handshake, but buffered data will still be readable from
	the socket buffer. This data will not be authenticated if the
	server-side TLS peer is expecting client certificate authentication,
	and is indistinguishable from valid TLS stream data. Data is limited
	in size to the amount that will fit in the buffer. (The TLS connection
	cannot directly be used for data exfiltration because the vulnerable
	code path requires that the connection be closed on initialization of
	the SSLSocket.)</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2023-40217</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2023-40217</url>
    </references>
    <dates>
      <discovery>2023-08-25</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>