Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1031370: python-werkzeug: CVE-2023-23934 CVE-2023-25577
21 views
Skip to first unread message
Salvatore Bonaccorso
Feb 15, 2023, 4:40:05 PM2/15/23
to
Source: python-werkzeug
Version: 2.2.2-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team <te...@security.debian.org>
Hi,
The following vulnerabilities were published for python-werkzeug.
CVE-2023-23934[0]:
| Werkzeug is a comprehensive WSGI web application library. Browsers may
| allow "nameless" cookies that look like `=value` instead of
| `key=value`. A vulnerable browser may allow a compromised application
| on an adjacent subdomain to exploit this to set a cookie like
| `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will
| parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug
| application is running next to a vulnerable or malicious subdomain
| which sets such a cookie using a vulnerable browser, the Werkzeug
| application will see the bad cookie value but the valid cookie key.
| The issue is fixed in Werkzeug 2.2.3.
CVE-2023-25577[1]:
| Werkzeug is a comprehensive WSGI web application library. Prior to
| version 2.2.3, Werkzeug's multipart form data parser will parse an
| unlimited number of parts, including file parts. Parts can be a small
| amount of bytes, but each requires CPU time to parse and may use more
| memory as Python data. If a request can be made to an endpoint that
| accesses `request.data`, `request.form`, `request.files`, or
| `request.get_data(parse_form_data=False)`, it can cause unexpectedly
| high resource usage. This allows an attacker to cause a denial of
| service by sending crafted multipart data to an endpoint that will
| parse it. The amount of CPU time required can block worker processes
| from handling legitimate requests. The amount of RAM required can
| trigger an out of memory kill of the process. Unlimited file parts can
| use up memory and file handles. If many concurrent requests are sent
| continuously, this can exhaust or kill all available workers. Version
| 2.2.3 contains a patch for this issue.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2023-23934
https://www.cve.org/CVERecord?id=CVE-2023-23934
[1] https://security-tracker.debian.org/tracker/CVE-2023-25577
https://www.cve.org/CVERecord?id=CVE-2023-25577
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
Version: 2.2.2-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team <te...@security.debian.org>
Hi,
The following vulnerabilities were published for python-werkzeug.
CVE-2023-23934[0]:
| Werkzeug is a comprehensive WSGI web application library. Browsers may
| allow "nameless" cookies that look like `=value` instead of
| `key=value`. A vulnerable browser may allow a compromised application
| on an adjacent subdomain to exploit this to set a cookie like
| `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will
| parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug
| application is running next to a vulnerable or malicious subdomain
| which sets such a cookie using a vulnerable browser, the Werkzeug
| application will see the bad cookie value but the valid cookie key.
| The issue is fixed in Werkzeug 2.2.3.
CVE-2023-25577[1]:
| Werkzeug is a comprehensive WSGI web application library. Prior to
| version 2.2.3, Werkzeug's multipart form data parser will parse an
| unlimited number of parts, including file parts. Parts can be a small
| amount of bytes, but each requires CPU time to parse and may use more
| memory as Python data. If a request can be made to an endpoint that
| accesses `request.data`, `request.form`, `request.files`, or
| `request.get_data(parse_form_data=False)`, it can cause unexpectedly
| high resource usage. This allows an attacker to cause a denial of
| service by sending crafted multipart data to an endpoint that will
| parse it. The amount of CPU time required can block worker processes
| from handling legitimate requests. The amount of RAM required can
| trigger an out of memory kill of the process. Unlimited file parts can
| use up memory and file handles. If many concurrent requests are sent
| continuously, this can exhaust or kill all available workers. Version
| 2.2.3 contains a patch for this issue.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2023-23934
https://www.cve.org/CVERecord?id=CVE-2023-23934
[1] https://security-tracker.debian.org/tracker/CVE-2023-25577
https://www.cve.org/CVERecord?id=CVE-2023-25577
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
Robin Gustafsson
Apr 20, 2023, 3:50:05 PM4/20/23
to
Hi,
I've submitted a merge request on Salsa to fix this.
Regards,
Robin
0 new messages