<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 12:38:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-6763 — Jetty URI parsing of invalid authority</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-6763</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Jetty, eclipse jetty&lt;/p&gt;
&lt;p&gt;Eclipse Jetty is a lightweight, highly scalable, Java-based web server and Servlet engine . It includes a utility class, HttpURI, for URI/URL parsing.&lt;/p&gt;
&lt;p&gt;The HttpURI class does insufficient validation on the authority segment of a URI.  However the behaviour of HttpURI
 differs from the common browsers in how it handles a URI that would be 
considered invalid if fully validated against the RRC.  Specifically HttpURI
 and the browser may differ on the value of the host extracted from an 
invalid URI and thus a combination of Jetty and a vulnerable browser may
 be vulnerable to a open redirect attack or to a SSRF attack if the URI 
is used after passing validation checks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Jetty, eclipse jetty&lt;/p&gt;
&lt;p&gt;Eclipse Jetty is a lightweight, highly scalable, Java-based web server and Servlet engine . It includes a utility class, HttpURI, for URI/URL parsing.&lt;/p&gt;
&lt;p&gt;The HttpURI class does insufficient validation on the authority segment of a URI.  However the behaviour of HttpURI
 differs from the common browsers in how it handles a URI that would be 
considered invalid if fully validated against the RRC.  Specifically HttpURI
 and the browser may differ on the value of the host extracted from an 
invalid URI and thus a combination of Jetty and a vulnerable browser may
 be vulnerable to a open redirect attack or to a SSRF attack if the URI 
is used after passing validation checks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-6763</guid>
    </item>
    <item>
      <title>GHSA-355h-qmc2-wpwf — Jetty has HTTP Request Smuggling via Chunked Extension Quoted-String Parsing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-355h-qmc2-wpwf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.eclipse.jetty:jetty-http&lt;/p&gt;
&lt;p&gt;### Description (as reported)&lt;/p&gt;
&lt;p&gt;Jetty incorrectly parses quoted strings in HTTP/1.1 chunked transfer encoding extension values, enabling request smuggling attacks.&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;This vulnerability is a new variant discovered while researching the &amp;#34;Funky Chunks&amp;#34; HTTP request smuggling techniques:
- https://w4ke.info/2025/06/18/funky-chunks.html
- https://w4ke.info/2025/10/29/funky-chunks-2.html&lt;/p&gt;
&lt;p&gt;The original research tested various chunk extension parsing differentials but did not test quoted-string handling within extension values.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;**RFC 9112 Section 7.1.1** defines chunked transfer encoding:
```
chunk = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
chunk-ext = *( BWS &amp;#34;;&amp;#34; BWS chunk-ext-name [ BWS &amp;#34;=&amp;#34; BWS chunk-ext-val ] )
chunk-ext-val = token / quoted-string
```&lt;/p&gt;
&lt;p&gt;**RFC 9110 Section 5.6.4** defines quoted-string:
```
quoted-string = DQUOTE *( qdtext / quoted-pair ) DQUOTE
```&lt;/p&gt;
&lt;p&gt;A quoted-string continues until the closing DQUOTE, and `\r\n` sequences are not permitted within the quotes.&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;Jetty terminates chunk header parsing at `\r\n` inside quoted strings instead of treating this as an error.&lt;/p&gt;
&lt;p&gt;**Expected (RFC compliant):**
```
Chunk: 1;a=&amp;#34;value\r\nhere&amp;#34;\r\n
         ^^^^^^^^^^^^^^^^^^ extension value
Body: [1 byte after the real \r\n]
```&lt;/p&gt;
&lt;p&gt;**Actual (jetty):**
```
Chunk: 1;a=&amp;#34;value
            ^^^^^ terminates here (WRONG)
Body: here&amp;#34;... treated as body/next request
```&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
import…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.eclipse.jetty:jetty-http&lt;/p&gt;
&lt;p&gt;### Description (as reported)&lt;/p&gt;
&lt;p&gt;Jetty incorrectly parses quoted strings in HTTP/1.1 chunked transfer encoding extension values, enabling request smuggling attacks.&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;This vulnerability is a new variant discovered while researching the &amp;#34;Funky Chunks&amp;#34; HTTP request smuggling techniques:
- https://w4ke.info/2025/06/18/funky-chunks.html
- https://w4ke.info/2025/10/29/funky-chunks-2.html&lt;/p&gt;
&lt;p&gt;The original research tested various chunk extension parsing differentials but did not test quoted-string handling within extension values.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;**RFC 9112 Section 7.1.1** defines chunked transfer encoding:
```
chunk = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
chunk-ext = *( BWS &amp;#34;;&amp;#34; BWS chunk-ext-name [ BWS &amp;#34;=&amp;#34; BWS chunk-ext-val ] )
chunk-ext-val = token / quoted-string
```&lt;/p&gt;
&lt;p&gt;**RFC 9110 Section 5.6.4** defines quoted-string:
```
quoted-string = DQUOTE *( qdtext / quoted-pair ) DQUOTE
```&lt;/p&gt;
&lt;p&gt;A quoted-string continues until the closing DQUOTE, and `\r\n` sequences are not permitted within the quotes.&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;Jetty terminates chunk header parsing at `\r\n` inside quoted strings instead of treating this as an error.&lt;/p&gt;
&lt;p&gt;**Expected (RFC compliant):**
```
Chunk: 1;a=&amp;#34;value\r\nhere&amp;#34;\r\n
         ^^^^^^^^^^^^^^^^^^ extension value
Body: [1 byte after the real \r\n]
```&lt;/p&gt;
&lt;p&gt;**Actual (jetty):**
```
Chunk: 1;a=&amp;#34;value
            ^^^^^ terminates here (WRONG)
Body: here&amp;#34;... treated as body/next request
```&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
import…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-355h-qmc2-wpwf</guid>
    </item>
  </channel>
</rss>
