https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 13:52:49 +0000 https://cve.radiocsirt.org/vuln/certfr-2017-avi-224 certfr-2017-avi-224 https://cve.radiocsirt.org/vuln/certfr-2017-avi-224 https://cve.radiocsirt.org/vuln/cnvd-2017-05037 cnvd-2017-05037 https://cve.radiocsirt.org/vuln/cnvd-2017-05037 https://cve.radiocsirt.org/vuln/euvd-2026-73528 EUVD-2026-73528 https://cve.radiocsirt.org/vuln/euvd-2026-73528 https://cve.radiocsirt.org/vuln/fkie_cve-2017-5647 <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-5647 https://cve.radiocsirt.org/vuln/ghsa-3gv7-3h64-78cm <p><strong>Affected:</strong> Maven: org.apache.tomcat:tomcat</p> <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> <p><strong>Affected:</strong> Maven: org.apache.tomcat:tomcat</p> <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> https://cve.radiocsirt.org/vuln/ghsa-3gv7-3h64-78cm https://cve.radiocsirt.org/vuln/gsd-2017-5647 gsd-2017-5647 https://cve.radiocsirt.org/vuln/gsd-2017-5647 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11468-1 <p>tomcat-9.0.36-8.4 on GA media</p> <p>tomcat-9.0.36-8.4 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11468-1 https://cve.radiocsirt.org/vuln/rhsa-2017:1801 <p>openssl: OCSP Status Request extension unbounded memory growth openssl: ECDSA P-256 timing attack key recovery SSL/TLS: Malformed plain-text ALERT packets could cause remote DoS log4j: Socket receiver deserialization vulnerability tomcat: Incorrect handling of pipelined requests when send file was used tomcat: Calls to application listeners did not use the appropriate facade object tomcat: Security constrained bypass in error page mechanism tomcat: Vary header not added by CORS filter leading to cache poisoning log4j: deserialization of untrusted data in SocketServer</p> <p>openssl: OCSP Status Request extension unbounded memory growth openssl: ECDSA P-256 timing attack key recovery SSL/TLS: Malformed plain-text ALERT packets could cause remote DoS log4j: Socket receiver deserialization vulnerability tomcat: Incorrect handling of pipelined requests when send file was used tomcat: Calls to application listeners did not use the appropriate facade object tomcat: Security constrained bypass in error page mechanism tomcat: Vary header not added by CORS filter leading to cache poisoning log4j: deserialization of untrusted data in SocketServer</p> https://cve.radiocsirt.org/vuln/rhsa-2017:1801 https://cve.radiocsirt.org/vuln/suse-su-2017:1229-1 <p>Security update for tomcat</p> <p>Security update for tomcat</p> https://cve.radiocsirt.org/vuln/suse-su-2017:1229-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-5647 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: tomcat7, Ubuntu:Pro:14.04:LTS: tomcat6, Ubuntu:16.04:LTS: tomcat8, Ubuntu:Pro:16.04:LTS: tomcat7</p> <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: tomcat7, Ubuntu:Pro:14.04:LTS: tomcat6, Ubuntu:16.04:LTS: tomcat8, Ubuntu:Pro:16.04:LTS: tomcat7</p> <p>A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-5647 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0528 <p>Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen, Dateien zu manipulieren, vertrauliche Informationen offenzulegen, seine Berechtigungen zu erweitern oder einen nicht spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen, Dateien zu manipulieren, vertrauliche Informationen offenzulegen, seine Berechtigungen zu erweitern oder einen nicht spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0528