Red Hat Security Advisory: python-twisted-web security update
An update for python-twisted-web is now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.
describes (2)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-10109US | critical9.8 | — | ||
In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with a content-length and a chunked encoding header, the content-length took prece… | ||||
| CVE-2020-10108US | critical9.8 | — | ||
In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with two content-length headers, it ignored the first header. When the second cont… | ||||
references
External citations — patches, advisories, analysis.
remediations (44)
- Fixedpython-twisted-web-0:12.1.0-7.el7_8.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Client Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Client Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Fixedpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
https://access.redhat.com/errata/RHSA-2020:1561 - Workaroundpython-twisted-web-0:12.1.0-7.el7_8.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Client Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Client Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.src as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
- Workaroundpython-twisted-web-0:12.1.0-7.el7_8.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
When python-twisted-web is used as the back-end of your infrastructure, you can partially mitigate the problem by ensuring that each request on the front-end component (e.g. proxy) is sent over a separate network connection to the python-twisted-web server. This will prevent interference between different users, but it will not prevent all possible attacks that can be performed, which would vary based on the infrastructure and application in use.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan