{ "data_type": "CVE", "data_format": "MITRE", "data_version": "4.0", "CVE_data_meta": { "ID": "CVE-2020-13943", "ASSIGNER": "security@apache.org", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "vendor_name": "n/a", "product": { "product_data": [ { "product_name": "Apache Tomcat", "version": { "version_data": [ { "version_value": "Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37, 8.5.0 to 8.5.57" } ] } } ] } } ] } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "Information Disclosure" } ] } ] }, "references": { "reference_data": [ { "refsource": "MISC", "name": "https://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E", "url": "https://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E" }, { "refsource": "MLIST", "name": "[debian-lts-announce] 20201014 [SECURITY] [DLA 2407-1] tomcat8 security update", "url": "https://lists.debian.org/debian-lts-announce/2020/10/msg00019.html" }, { "refsource": "CONFIRM", "name": "https://security.netapp.com/advisory/ntap-20201016-0007/", "url": "https://security.netapp.com/advisory/ntap-20201016-0007/" }, { "refsource": "SUSE", "name": "openSUSE-SU-2020:1799", "url": "http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00002.html" }, { "refsource": "SUSE", "name": "openSUSE-SU-2020:1842", "url": "http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00021.html" }, { "refsource": "DEBIAN", "name": "DSA-4835", "url": "https://www.debian.org/security/2021/dsa-4835" } ] }, "description": { "description_data": [ { "lang": "eng", "value": "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." } ] } }