You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected versions of this package are vulnerable to HTTP Request Smuggling due to the improper validation of Transfer-Encoding headers. An attacker can bypass security restrictions and access restricted endpoints by crafting requests with conflicting Transfer-Encoding headers.
Notes:
This is only exploitable if users have a network path which does not filter out invalid requests;
Users are advised to block access to restricted endpoints via a firewall or other mechanism until a fix can be developed.
This issue arises from the application's incorrectly processing of requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified.
Completion Criteria
Upgrade Gunicorn once patched version is available
The text was updated successfully, but these errors were encountered:
Introduced through
[email protected]
Exploit maturity
PROOF OF CONCEPT
Detailed paths
Introduced through: [email protected] › [email protected]
Fix: No remediation path available.
Security information
Factors contributing to the scoring:
Snyk: CVSS 7.5 - High Severity
NVD: Not available. NVD has not yet published its analysis.
Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview
gunicorn is a Python WSGI HTTP Server for UNIX
Affected versions of this package are vulnerable to HTTP Request Smuggling due to the improper validation of Transfer-Encoding headers. An attacker can bypass security restrictions and access restricted endpoints by crafting requests with conflicting Transfer-Encoding headers.
Notes:
This is only exploitable if users have a network path which does not filter out invalid requests;
Users are advised to block access to restricted endpoints via a firewall or other mechanism until a fix can be developed.
This issue arises from the application's incorrectly processing of requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified.
Completion Criteria
The text was updated successfully, but these errors were encountered: