https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:04:27 +0000 https://cve.radiocsirt.org/vuln/alsa-2019:1529 <p><strong>Affected:</strong> AlmaLinux:8: apache-commons-collections, AlmaLinux:8: apache-commons-lang, AlmaLinux:8: bea-stax-api, AlmaLinux:8: glassfish-fastinfoset, AlmaLinux:8: glassfish-jaxb-api, AlmaLinux:8: glassfish-jaxb-core, AlmaLinux:8: glassfish-jaxb-runtime, AlmaLinux:8: glassfish-jaxb-txw2, AlmaLinux:8: jackson-module-jaxb-annotations, AlmaLinux:8: jakarta-commons-httpclient and 15 more</p> <p>The Public Key Infrastructure (PKI) Deps module contains fundamental packages required as dependencies for the pki-core module by AlmaLinux Certificate System.</p> <p>Security Fix(es):</p> <p>* tomcat: Due to a mishandling of close in NIO/NIO2 connectors user sessions can get mixed up (CVE-2018-8037)</p> <p>* tomcat: Insecure defaults in CORS filter enable &#39;supportsCredentials&#39; for all origins (CVE-2018-8014)</p> <p>* tomcat: Open redirect in default servlet (CVE-2018-11784)</p> <p>* tomcat: Host name verification missing in WebSocket client (CVE-2018-8034)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p><strong>Affected:</strong> AlmaLinux:8: apache-commons-collections, AlmaLinux:8: apache-commons-lang, AlmaLinux:8: bea-stax-api, AlmaLinux:8: glassfish-fastinfoset, AlmaLinux:8: glassfish-jaxb-api, AlmaLinux:8: glassfish-jaxb-core, AlmaLinux:8: glassfish-jaxb-runtime, AlmaLinux:8: glassfish-jaxb-txw2, AlmaLinux:8: jackson-module-jaxb-annotations, AlmaLinux:8: jakarta-commons-httpclient and 15 more</p> <p>The Public Key Infrastructure (PKI) Deps module contains fundamental packages required as dependencies for the pki-core module by AlmaLinux Certificate System.</p> <p>Security Fix(es):</p> <p>* tomcat: Due to a mishandling of close in NIO/NIO2 connectors user sessions can get mixed up (CVE-2018-8037)</p> <p>* tomcat: Insecure defaults in CORS filter enable &#39;supportsCredentials&#39; for all origins (CVE-2018-8014)</p> <p>* tomcat: Open redirect in default servlet (CVE-2018-11784)</p> <p>* tomcat: Host name verification missing in WebSocket client (CVE-2018-8034)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2019:1529 https://cve.radiocsirt.org/vuln/bdu:2019-04412 bdu:2019-04412 https://cve.radiocsirt.org/vuln/bdu:2019-04412 https://cve.radiocsirt.org/vuln/certfr-2018-avi-356 certfr-2018-avi-356 https://cve.radiocsirt.org/vuln/certfr-2018-avi-356 https://cve.radiocsirt.org/vuln/cnvd-2018-13746 cnvd-2018-13746 https://cve.radiocsirt.org/vuln/cnvd-2018-13746 https://cve.radiocsirt.org/vuln/euvd-2026-165268 EUVD-2026-165268 https://cve.radiocsirt.org/vuln/euvd-2026-165268 https://cve.radiocsirt.org/vuln/fkie_cve-2018-8037 <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-8037 https://cve.radiocsirt.org/vuln/ghsa-6v52-mj5r-7j2m <p><strong>Affected:</strong> Maven: org.apache.tomcat.embed:tomcat-embed-core</p> <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> <p><strong>Affected:</strong> Maven: org.apache.tomcat.embed:tomcat-embed-core</p> <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> https://cve.radiocsirt.org/vuln/ghsa-6v52-mj5r-7j2m https://cve.radiocsirt.org/vuln/gsd-2018-8037 gsd-2018-8037 https://cve.radiocsirt.org/vuln/gsd-2018-8037 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-2018:2867 <p>tomcat: Due to a mishandling of close in NIO/NIO2 connectors user sessions can get mixed up tomcat: Open redirect in default servlet</p> <p>tomcat: Due to a mishandling of close in NIO/NIO2 connectors user sessions can get mixed up tomcat: Open redirect in default servlet</p> https://cve.radiocsirt.org/vuln/rhsa-2018:2867 https://cve.radiocsirt.org/vuln/suse-su-2018:2699-1 <p>Security update for tomcat</p> <p>Security update for tomcat</p> https://cve.radiocsirt.org/vuln/suse-su-2018:2699-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-8037 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: tomcat8</p> <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: tomcat8</p> <p>If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-8037 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