Authentication Bypass by Primary Weakness Affecting python39:3.9/python39-pysocks package, versions <0:1.7.1-4.module+el8.4.0+9822+20bf1249


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.09% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-PYTHON39-6031344
  • published31 Aug 2023
  • disclosed25 Aug 2023

Introduced: 25 Aug 2023

CVE-2023-40217  (opens in a new tab)
CWE-305  (opens in a new tab)

How to fix?

Upgrade RHEL:8 python39:3.9/python39-pysocks to version 0:1.7.1-4.module+el8.4.0+9822+20bf1249 or higher.
This issue was patched in RHSA-2023:6068.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python39:3.9/python39-pysocks package and not the python39:3.9/python39-pysocks package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.)

CVSS Scores

version 3.1