<?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://vulnerability.circl.lu</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>Wed, 07 Oct 2026 03:04:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2018-1000005</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2018-1000005</link>
      <description>&lt;p&gt;libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn&amp;#39;t updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn&amp;#39;t updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2018-1000005</guid>
    </item>
    <item>
      <title>USN-3554-1 — curl vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-3554-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: curl, Ubuntu:16.04:LTS: curl&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrectly handled certain data. An attacker
could possibly use this to cause a denial of service or even to get access
to sensitive data. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10.&lt;/p&gt;
&lt;p&gt;It was discovered that curl could accidentally leak authentication data.
An attacker could possibly use this to get access to sensitive information.
(CVE-2018-1000007)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: curl, Ubuntu:16.04:LTS: curl&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrectly handled certain data. An attacker
could possibly use this to cause a denial of service or even to get access
to sensitive data. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10.&lt;/p&gt;
&lt;p&gt;It was discovered that curl could accidentally leak authentication data.
An attacker could possibly use this to get access to sensitive information.
(CVE-2018-1000007)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-3554-1</guid>
    </item>
  </channel>
</rss>
