https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 21:48:34 +0000 https://cve.radiocsirt.org/vuln/bdu:2022-05762 bdu:2022-05762 https://cve.radiocsirt.org/vuln/bdu:2022-05762 https://cve.radiocsirt.org/vuln/cnvd-2022-21483 cnvd-2022-21483 https://cve.radiocsirt.org/vuln/cnvd-2022-21483 https://cve.radiocsirt.org/vuln/euvd-2026-234307 EUVD-2026-234307 https://cve.radiocsirt.org/vuln/euvd-2026-234307 https://cve.radiocsirt.org/vuln/fkie_cve-2022-24761 <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-24761 https://cve.radiocsirt.org/vuln/ghsa-4f7p-27jc-3c36 <p><strong>Affected:</strong> PyPI: waitress</p> <p>### Impact</p> <p>When using Waitress behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends.</p> <p>This would allow requests to be smuggled via the front-end proxy to waitress and later behavior.</p> <p>There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory:</p> <p>- The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits. - Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters</p> <p>### Patches</p> <p>This has been fixed in Waitress 2.1.1</p> <p>### Workarounds</p> <p>When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> <p>### References</p> <p>- https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory: * Open an issue in [the Github issue tracker](https://github.com/Pylons/waitress/issues) (if not security related/sensitive) * Email us at [pylons-project-security…</p> <p><strong>Affected:</strong> PyPI: waitress</p> <p>### Impact</p> <p>When using Waitress behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends.</p> <p>This would allow requests to be smuggled via the front-end proxy to waitress and later behavior.</p> <p>There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory:</p> <p>- The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits. - Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters</p> <p>### Patches</p> <p>This has been fixed in Waitress 2.1.1</p> <p>### Workarounds</p> <p>When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> <p>### References</p> <p>- https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory: * Open an issue in [the Github issue tracker](https://github.com/Pylons/waitress/issues) (if not security related/sensitive) * Email us at [pylons-project-security…</p> https://cve.radiocsirt.org/vuln/ghsa-4f7p-27jc-3c36 https://cve.radiocsirt.org/vuln/gsd-2022-24761 gsd-2022-24761 https://cve.radiocsirt.org/vuln/gsd-2022-24761 https://cve.radiocsirt.org/vuln/msrc_cve-2022-24761 msrc_CVE-2022-24761 https://cve.radiocsirt.org/vuln/msrc_cve-2022-24761 https://cve.radiocsirt.org/vuln/oesa-2022-1643 <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: python-waitress, openEuler:20.03-LTS-SP3: python-waitress, openEuler:22.03-LTS: python-waitress</p> <p>Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.5+. It is also known to run on PyPy 1.6.0+ on UNIX. It supports HTTP/1.0 and HTTP/1.1. Security Fix(es): Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not ha…</p> <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: python-waitress, openEuler:20.03-LTS-SP3: python-waitress, openEuler:22.03-LTS: python-waitress</p> <p>Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.5+. It is also known to run on PyPy 1.6.0+ on UNIX. It supports HTTP/1.0 and HTTP/1.1. Security Fix(es): Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not ha…</p> https://cve.radiocsirt.org/vuln/oesa-2022-1643 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11942-1 <p>python310-waitress-2.1.1-1.1 on GA media</p> <p>python310-waitress-2.1.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11942-1 https://cve.radiocsirt.org/vuln/pysec-2022-169 <p><strong>Affected:</strong> PyPI: waitress</p> <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> <p><strong>Affected:</strong> PyPI: waitress</p> <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> https://cve.radiocsirt.org/vuln/pysec-2022-169 https://cve.radiocsirt.org/vuln/rhsa-2022:1253 <p>waitress: Inconsistent Interpretation of HTTP Requests (&#39;HTTP Request Smuggling&#39;)</p> <p>waitress: Inconsistent Interpretation of HTTP Requests (&#39;HTTP Request Smuggling&#39;)</p> https://cve.radiocsirt.org/vuln/rhsa-2022:1253 https://cve.radiocsirt.org/vuln/suse-su-2022:3583-1 <p>Security update for python-waitress</p> <p>Security update for python-waitress</p> https://cve.radiocsirt.org/vuln/suse-su-2022:3583-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-24761 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: waitress, Ubuntu:22.04:LTS: waitress</p> <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: waitress, Ubuntu:22.04:LTS: waitress</p> <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python&#39;s `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-24761 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2556 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenStack ausnutzen, um einen Request Smuggling Angriff durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenStack ausnutzen, um einen Request Smuggling Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2556