<?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>Sat, 03 Oct 2026 12:11:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16785 — HTTP Request Smuggling: LF vs CRLF handling in Waitress</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2019-16785</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Pylons Waitress&lt;/p&gt;
&lt;p&gt;Waitress through version 1.3.1 implemented a &amp;#34;MAY&amp;#34; part of the RFC7230 which states: &amp;#34;Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.&amp;#34; Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Pylons Waitress&lt;/p&gt;
&lt;p&gt;Waitress through version 1.3.1 implemented a &amp;#34;MAY&amp;#34; part of the RFC7230 which states: &amp;#34;Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.&amp;#34; Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2019-16785</guid>
    </item>
  </channel>
</rss>
