https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:07:39 +0000 https://cve.radiocsirt.org/vuln/certfr-2021-avi-417 certfr-2021-avi-417 https://cve.radiocsirt.org/vuln/certfr-2021-avi-417 https://cve.radiocsirt.org/vuln/cnvd-2021-29467 cnvd-2021-29467 https://cve.radiocsirt.org/vuln/cnvd-2021-29467 https://cve.radiocsirt.org/vuln/euvd-2026-215946 EUVD-2026-215946 https://cve.radiocsirt.org/vuln/euvd-2026-215946 https://cve.radiocsirt.org/vuln/fkie_cve-2021-22696 <p>CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a &#34;request&#34; parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the &#34;request_uri&#34; parameter. CXF was not validating the &#34;request_uri&#34; parameter (apart from ensuring it uses &#34;https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.</p> <p>CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a &#34;request&#34; parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the &#34;request_uri&#34; parameter. CXF was not validating the &#34;request_uri&#34; parameter (apart from ensuring it uses &#34;https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-22696 https://cve.radiocsirt.org/vuln/ghsa-7q4h-pj78-j7vg <p><strong>Affected:</strong> Maven: org.apache.cxf:cxf, Maven: org.apache.cxf:apache-cxf</p> <p>CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a &#34;request&#34; parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the &#34;request_uri&#34; parameter. CXF was not validating the &#34;request_uri&#34; parameter (apart from ensuring it uses &#34;https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.</p> <p><strong>Affected:</strong> Maven: org.apache.cxf:cxf, Maven: org.apache.cxf:apache-cxf</p> <p>CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a &#34;request&#34; parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the &#34;request_uri&#34; parameter. CXF was not validating the &#34;request_uri&#34; parameter (apart from ensuring it uses &#34;https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.</p> https://cve.radiocsirt.org/vuln/ghsa-7q4h-pj78-j7vg https://cve.radiocsirt.org/vuln/gsd-2021-22696 gsd-2021-22696 https://cve.radiocsirt.org/vuln/gsd-2021-22696 https://cve.radiocsirt.org/vuln/rhsa-2021:5134 <p>nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties poi: a specially crafted Microsoft Excel document allows attacker to read files from the local filesystem mysql-connector-java: allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors which could result in unauthorized update, insert or delete mysql-connector-java: allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors which could result in unauthorized update, insert or delete log4j: improper validation of certificate with host mismatch in SMTP appender batik: SSRF due to improper input validation by the NodePickerPanel xmlgraphics-commons: SSRF due to improper input validation by the XMPParser tomcat: Apache Tomcat HTTP/2 Request mix-up libthrift: potential DoS when processing untrusted payloads bouncycastle: Timing issue within the EC math library groovy: OS temporary directory leads to information disclosure tomcat: HTTP/2 request header mix-up XStream: remote code execution due to insecure XML deserialization when relying on blocklists XStream: arbitrary file deletion on the local host when unmarshalling jetty: buffer not correctly recycled in Gzip Request inflation jetty: request containing multiple Accept headers with a large number of &#34;quality&#34; parameters may lead to DoS undertow: special character in query results in server errors jackson-dataformat-cbor: Unchecked allocation…</p> <p>nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties poi: a specially crafted Microsoft Excel document allows attacker to read files from the local filesystem mysql-connector-java: allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors which could result in unauthorized update, insert or delete mysql-connector-java: allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors which could result in unauthorized update, insert or delete log4j: improper validation of certificate with host mismatch in SMTP appender batik: SSRF due to improper input validation by the NodePickerPanel xmlgraphics-commons: SSRF due to improper input validation by the XMPParser tomcat: Apache Tomcat HTTP/2 Request mix-up libthrift: potential DoS when processing untrusted payloads bouncycastle: Timing issue within the EC math library groovy: OS temporary directory leads to information disclosure tomcat: HTTP/2 request header mix-up XStream: remote code execution due to insecure XML deserialization when relying on blocklists XStream: arbitrary file deletion on the local host when unmarshalling jetty: buffer not correctly recycled in Gzip Request inflation jetty: request containing multiple Accept headers with a large number of &#34;quality&#34; parameters may lead to DoS undertow: special character in query results in server errors jackson-dataformat-cbor: Unchecked allocation…</p> https://cve.radiocsirt.org/vuln/rhsa-2021:5134 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0227 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erweitern, Administratorrechte zu erlangen, beliebigen Programmcode auszuführen, Informationen offenzulegen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erweitern, Administratorrechte zu erlangen, beliebigen Programmcode auszuführen, Informationen offenzulegen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0227