Homepage
About Snyk

Authentication Bypass by Primary Weakness Affecting python27-libs package, versions <0:2.7.18-2.148.amzn1

0.0
high

Snyk CVSS

    Attack Complexity Low
    Scope Changed
    Integrity High

    Threat Intelligence

    EPSS 0.05% (17th percentile)
Expand this section
NVD
5.3 medium
Expand this section
SUSE
7.4 high
Expand this section
Red Hat
8.6 high

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 ID SNYK-AMZN201803-PYTHON27LIBS-6045909
  • published 4 Nov 2023
  • disclosed 25 Aug 2023
Report a new vulnerability Found a mistake?

Introduced: 25 Aug 2023

CVE-2023-40217 Open this link in a new tab
CWE-305 Open this link in a new tab

How to fix?

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.148.amzn1 or higher.
This issue was patched in ALAS-2023-1876.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 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.)