Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GHSA-w3h3-4rj7-4ph4] Request smuggling leading to endpoint restriction bypass in Gunicorn #4275

Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-w3h3-4rj7-4ph4",
"modified": "2024-04-16T23:23:26Z",
"modified": "2024-04-16T23:24:40Z",
"published": "2024-04-16T00:30:32Z",
"aliases": [
"CVE-2024-1135"
],
"summary": "Request smuggling leading to endpoint restriction bypass in Gunicorn",
"details": "Gunicorn fails to properly validate Transfer-Encoding headers, leading to HTTP Request Smuggling (HRS) vulnerabilities. By crafting requests with conflicting Transfer-Encoding headers, attackers can bypass security restrictions and access restricted endpoints. This issue is due to Gunicorn's handling of Transfer-Encoding headers, where it incorrectly processes requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified. This vulnerability has been shown to allow access to endpoints restricted by gunicorn.\n\nTo be affected users must have a network path which does not filter out invalid requests. These users are advised to block access to restricted endpoints via a firewall or other mechanism if they are unable to update. ",
"details": "Gunicorn fails to properly validate Transfer-Encoding headers, leading to HTTP Request Smuggling (HRS) vulnerabilities. By crafting requests with conflicting Transfer-Encoding headers, attackers can bypass security restrictions and access restricted endpoints. This issue is due to Gunicorn's handling of Transfer-Encoding headers, where it incorrectly processes requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified. This vulnerability has been shown to allow access to endpoints restricted by gunicorn. This issue has been addressed in version 22.0.0.\n\nTo be affected users must have a network path which does not filter out invalid requests. These users are advised to block access to restricted endpoints via a firewall or other mechanism if they are unable to update. ",
"severity": [
{
"type": "CVSS_V3",
Expand Down Expand Up @@ -48,6 +48,10 @@
"type": "PACKAGE",
"url": "https://github.com/benoitc/gunicorn"
},
{
"type": "WEB",
"url": "https://github.com/benoitc/gunicorn/releases/tag/22.0.0"
},
{
"type": "WEB",
"url": "https://huntr.com/bounties/22158e34-cfd5-41ad-97e0-a780773d96c1"
Expand Down