If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
References
Link | Resource |
---|---|
http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00002.html | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00021.html | Broken Link |
https://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E | Vendor Advisory |
https://lists.debian.org/debian-lts-announce/2020/10/msg00019.html | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20201016-0007/ | Third Party Advisory |
https://www.debian.org/security/2021/dsa-4835 | Third Party Advisory |
https://www.oracle.com/security-alerts/cpuApr2021.html | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
No history.
Information
Published : 2020-10-12 14:15
Updated : 2024-02-28 18:08
NVD link : CVE-2020-13943
Mitre link : CVE-2020-13943
CVE.ORG link : CVE-2020-13943
JSON object : View
Products Affected
oracle
- instantis_enterprisetrack
- sd-wan_edge
debian
- debian_linux
apache
- tomcat
CWE