<?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://127.0.0.1:10001</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, 21 Nov 2026 05:22:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-18678</title>
      <link>https://127.0.0.1:10001/vuln/cve-2019-18678</link>
      <description>&lt;p&gt;An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2019-18678</guid>
    </item>
    <item>
      <title>USN-4213-1 — squid, squid3 vulnerabilities</title>
      <link>https://127.0.0.1:10001/vuln/usn-4213-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: squid3, Ubuntu:18.04:LTS: squid3&lt;/p&gt;
&lt;p&gt;Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain URN requests. A remote attacker could possibly use this
issue to bypass access checks and access restricted servers. This issue was
only addressed in Ubuntu 19.04 and Ubuntu 19.10. (CVE-2019-12523)&lt;/p&gt;
&lt;p&gt;Jeriko One discovered that Squid incorrectly handed URN responses. A remote
attacker could use this issue to cause Squid to crash, resulting in a
denial of service, or possibly execute arbitrary code. (CVE-2019-12526)&lt;/p&gt;
&lt;p&gt;Alex Rousskov discovered that Squid incorrectly handled certain strings. A
remote attacker could possibly use this issue to cause Squid to crash,
resulting in a denial of service. This issue only affected Ubuntu 19.04.
(CVE-2019-12854)&lt;/p&gt;
&lt;p&gt;Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain input. A remote attacker could use this issue to cause
Squid to crash, resulting in a denial of service, or possibly execute
arbitrary code. This issue was only addressed in Ubuntu 19.04 and Ubuntu
19.10. (CVE-2019-18676)&lt;/p&gt;
&lt;p&gt;Kristoffer Danielsson discovered that Squid incorrectly handled certain
messages. This issue could result in traffic being redirected to origins
it should not be delivered to. (CVE-2019-18677)&lt;/p&gt;
&lt;p&gt;Régis Leroy discovered that Squid incorrectly handled certain HTTP
request headers. A remote attacker could use this to smuggle HTTP requests
and corrupt caches with arbitrary content. (CVE-2019-18678)&lt;/p&gt;
&lt;p&gt;David Fifield discovered that Squid incorrectly ha…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: squid3, Ubuntu:18.04:LTS: squid3&lt;/p&gt;
&lt;p&gt;Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain URN requests. A remote attacker could possibly use this
issue to bypass access checks and access restricted servers. This issue was
only addressed in Ubuntu 19.04 and Ubuntu 19.10. (CVE-2019-12523)&lt;/p&gt;
&lt;p&gt;Jeriko One discovered that Squid incorrectly handed URN responses. A remote
attacker could use this issue to cause Squid to crash, resulting in a
denial of service, or possibly execute arbitrary code. (CVE-2019-12526)&lt;/p&gt;
&lt;p&gt;Alex Rousskov discovered that Squid incorrectly handled certain strings. A
remote attacker could possibly use this issue to cause Squid to crash,
resulting in a denial of service. This issue only affected Ubuntu 19.04.
(CVE-2019-12854)&lt;/p&gt;
&lt;p&gt;Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain input. A remote attacker could use this issue to cause
Squid to crash, resulting in a denial of service, or possibly execute
arbitrary code. This issue was only addressed in Ubuntu 19.04 and Ubuntu
19.10. (CVE-2019-18676)&lt;/p&gt;
&lt;p&gt;Kristoffer Danielsson discovered that Squid incorrectly handled certain
messages. This issue could result in traffic being redirected to origins
it should not be delivered to. (CVE-2019-18677)&lt;/p&gt;
&lt;p&gt;Régis Leroy discovered that Squid incorrectly handled certain HTTP
request headers. A remote attacker could use this to smuggle HTTP requests
and corrupt caches with arbitrary content. (CVE-2019-18678)&lt;/p&gt;
&lt;p&gt;David Fifield discovered that Squid incorrectly ha…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/usn-4213-1</guid>
    </item>
  </channel>
</rss>
