https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:56:14 +0000 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119 certfr-2024-avi-0119 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119 https://cve.radiocsirt.org/vuln/euvd-2026-198642 EUVD-2026-198642 https://cve.radiocsirt.org/vuln/euvd-2026-198642 https://cve.radiocsirt.org/vuln/fkie_cve-2023-38199 <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion&#34; between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.</p> <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion&#34; between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-38199 https://cve.radiocsirt.org/vuln/ghsa-662c-vg67-m327 <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not block multiple Content-Type headers, which might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion.&#34; This occurs when the web application relies on only the last Content-Type header.</p> <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not block multiple Content-Type headers, which might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion.&#34; This occurs when the web application relies on only the last Content-Type header.</p> https://cve.radiocsirt.org/vuln/ghsa-662c-vg67-m327 https://cve.radiocsirt.org/vuln/gsd-2023-38199 gsd-2023-38199 https://cve.radiocsirt.org/vuln/gsd-2023-38199 https://cve.radiocsirt.org/vuln/icsa-24-046-15 <p>A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a…</p> <p>A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a…</p> https://cve.radiocsirt.org/vuln/icsa-24-046-15 https://cve.radiocsirt.org/vuln/opensuse-su-2024:13187-1 <p>owasp-modsecurity-crs-3.3.5-1.1 on GA media</p> <p>owasp-modsecurity-crs-3.3.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:13187-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38199 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: modsecurity-crs, Ubuntu:18.04:LTS: modsecurity-crs, Ubuntu:20.04:LTS: modsecurity-crs, Ubuntu:22.04:LTS: modsecurity-crs, Ubuntu:24.04:LTS: modsecurity-crs, Ubuntu:25.10: modsecurity-crs, Ubuntu:26.04:LTS: modsecurity-crs</p> <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion&#34; between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: modsecurity-crs, Ubuntu:18.04:LTS: modsecurity-crs, Ubuntu:20.04:LTS: modsecurity-crs, Ubuntu:22.04:LTS: modsecurity-crs, Ubuntu:24.04:LTS: modsecurity-crs, Ubuntu:25.10: modsecurity-crs, Ubuntu:26.04:LTS: modsecurity-crs</p> <p>coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka &#34;Content-Type confusion&#34; between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38199