https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:50:32 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-05682 bdu:2023-05682 https://cve.radiocsirt.org/vuln/bdu:2023-05682 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0705 certfr-2023-avi-0705 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0705 https://cve.radiocsirt.org/vuln/cleanstart-2026-if26545 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: apache-hive</p> <p>Package apache-hive version 4.0.1-r1 fixes 27 vulnerabilities: CVE-2024-47561, CVE-2024-7254, CVE-2024-47554, CVE-2022-41881, CVE-2023-34462...</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: apache-hive</p> <p>Package apache-hive version 4.0.1-r1 fixes 27 vulnerabilities: CVE-2024-47561, CVE-2024-7254, CVE-2024-47554, CVE-2022-41881, CVE-2023-34462...</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-if26545 https://cve.radiocsirt.org/vuln/euvd-2026-216342 EUVD-2026-216342 https://cve.radiocsirt.org/vuln/euvd-2026-216342 https://cve.radiocsirt.org/vuln/fkie_cve-2023-26049 <p>Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.</p> <p>Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-26049 https://cve.radiocsirt.org/vuln/ghsa-p26g-97m4-6q7c <p><strong>Affected:</strong> Maven: org.eclipse.jetty:jetty-server</p> <p>Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism.</p> <p>If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered.</p> <p>So, a cookie header such as:</p> <p>`DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name `DISPLAY_LANGUAGE` and a value of `b; JSESSIONID=1337; c=d`</p> <p>instead of 3 separate cookies.</p> <p>### Impact This has security implications because if, say, `JSESSIONID` is an `HttpOnly` cookie, and the `DISPLAY_LANGUAGE` cookie value is rendered on the page, an attacker can smuggle the `JSESSIONID` cookie into the `DISPLAY_LANGUAGE` cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server.</p> <p>### Patches * 9.4.51.v20230217 - via PR #9352 * 10.0.15 - via PR #9339 * 11.0.15 - via PR #9339</p> <p>### Workarounds No workarounds</p> <p>### References * https://www.rfc-editor.org/rfc/rfc2965 * https://www.rfc-editor.org/rfc/rfc6265</p> <p><strong>Affected:</strong> Maven: org.eclipse.jetty:jetty-server</p> <p>Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism.</p> <p>If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered.</p> <p>So, a cookie header such as:</p> <p>`DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name `DISPLAY_LANGUAGE` and a value of `b; JSESSIONID=1337; c=d`</p> <p>instead of 3 separate cookies.</p> <p>### Impact This has security implications because if, say, `JSESSIONID` is an `HttpOnly` cookie, and the `DISPLAY_LANGUAGE` cookie value is rendered on the page, an attacker can smuggle the `JSESSIONID` cookie into the `DISPLAY_LANGUAGE` cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server.</p> <p>### Patches * 9.4.51.v20230217 - via PR #9352 * 10.0.15 - via PR #9339 * 11.0.15 - via PR #9339</p> <p>### Workarounds No workarounds</p> <p>### References * https://www.rfc-editor.org/rfc/rfc2965 * https://www.rfc-editor.org/rfc/rfc6265</p> https://cve.radiocsirt.org/vuln/ghsa-p26g-97m4-6q7c https://cve.radiocsirt.org/vuln/gsd-2023-26049 gsd-2023-26049 https://cve.radiocsirt.org/vuln/gsd-2023-26049 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12949-1 <p>jetty-annotations-9.4.51-1.1 on GA media</p> <p>jetty-annotations-9.4.51-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:12949-1 https://cve.radiocsirt.org/vuln/rhsa-2023:5165 <p>netty-codec: Bzip2Decoder doesn&#39;t allow setting size restrictions for decompressed data netty-codec: SnappyFrameDecoder doesn&#39;t restrict chunk length and may buffer skippable chunks in an unnecessary way SnakeYaml: Constructor Deserialization Remote Code Execution netty: world readable temporary file containing sensitive data scala: deserialization gadget chain RESTEasy: creation of insecure temp files guava: insecure temporary directory creation okio: GzipSource class improper exception handling jetty-server: OutOfMemoryError for large multipart without filename read via request.getParameter() jetty-server: Cookie parsing of quoted values can exfiltrate values from other cookies bouncycastle: potential blind LDAP injection attack using a self-signed certificate snappy-java: Integer overflow in shuffle leads to DoS snappy-java: Integer overflow in compress leads to DoS snappy-java: Unchecked chunk length leads to DoS netty: SniHandler 16MB allocation leads to OOM</p> <p>netty-codec: Bzip2Decoder doesn&#39;t allow setting size restrictions for decompressed data netty-codec: SnappyFrameDecoder doesn&#39;t restrict chunk length and may buffer skippable chunks in an unnecessary way SnakeYaml: Constructor Deserialization Remote Code Execution netty: world readable temporary file containing sensitive data scala: deserialization gadget chain RESTEasy: creation of insecure temp files guava: insecure temporary directory creation okio: GzipSource class improper exception handling jetty-server: OutOfMemoryError for large multipart without filename read via request.getParameter() jetty-server: Cookie parsing of quoted values can exfiltrate values from other cookies bouncycastle: potential blind LDAP injection attack using a self-signed certificate snappy-java: Integer overflow in shuffle leads to DoS snappy-java: Integer overflow in compress leads to DoS snappy-java: Unchecked chunk length leads to DoS netty: SniHandler 16MB allocation leads to OOM</p> https://cve.radiocsirt.org/vuln/rhsa-2023:5165 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-26049 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: jetty, Ubuntu:16.04:LTS: jetty</p> <p>Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: jetty, Ubuntu:16.04:LTS: jetty</p> <p>Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `&#34;` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE=&#34;b; JSESSIONID=1337; c=d&#34;` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-26049 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1009 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Eclipse Jetty ausnutzen, um einen Denial of Service Angriff durchzuführen oder Informationen offenzulegen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Eclipse Jetty ausnutzen, um einen Denial of Service Angriff durchzuführen oder Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1009