<?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>Tue, 06 Oct 2026 16:02:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2016-8622</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2016-8622</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The Curl Project curl&lt;/p&gt;
&lt;p&gt;The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get either just truncated or both truncated and turned negative. That could then lead to libcurl writing outside of its heap based buffer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The Curl Project curl&lt;/p&gt;
&lt;p&gt;The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get either just truncated or both truncated and turned negative. That could then lead to libcurl writing outside of its heap based buffer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2016-8622</guid>
    </item>
    <item>
      <title>USN-3123-1 — curl vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-3123-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 reused client certificates when
built with NSS. A remote attacker could possibly use this issue to hijack
the authentication of a TLS connection. (CVE-2016-7141)&lt;/p&gt;
&lt;p&gt;Nguyen Vu Hoang discovered that curl incorrectly handled escaping certain
strings. A remote attacker could possibly use this issue to cause curl to
crash, resulting in a denial of service, or possibly execute arbitrary
code. (CVE-2016-7167)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrectly handled storing cookies. A remote
attacker could possibly use this issue to inject cookies for arbitrary
domains in the cookie jar. (CVE-2016-8615)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled case when comparing user
names and passwords. A remote attacker with knowledge of a case-insensitive
version of the correct password could possibly use this issue to cause
a connection to be reused. (CVE-2016-8616)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when encoding to
base64. A remote attacker could possibly use this issue to cause curl to
crash, resulting in a denial of service, or possibly execute arbitrary
code. (CVE-2016-8617)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when preparing
formatted output. A remote attacker could possibly use this issue to cause
curl to crash, resulting in a denial of service, or possibly execute
arbitrary code. (CVE-2016-8618)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when performing
Kerberos authentication. A remote attacker could pos…&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 reused client certificates when
built with NSS. A remote attacker could possibly use this issue to hijack
the authentication of a TLS connection. (CVE-2016-7141)&lt;/p&gt;
&lt;p&gt;Nguyen Vu Hoang discovered that curl incorrectly handled escaping certain
strings. A remote attacker could possibly use this issue to cause curl to
crash, resulting in a denial of service, or possibly execute arbitrary
code. (CVE-2016-7167)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrectly handled storing cookies. A remote
attacker could possibly use this issue to inject cookies for arbitrary
domains in the cookie jar. (CVE-2016-8615)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled case when comparing user
names and passwords. A remote attacker with knowledge of a case-insensitive
version of the correct password could possibly use this issue to cause
a connection to be reused. (CVE-2016-8616)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when encoding to
base64. A remote attacker could possibly use this issue to cause curl to
crash, resulting in a denial of service, or possibly execute arbitrary
code. (CVE-2016-8617)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when preparing
formatted output. A remote attacker could possibly use this issue to cause
curl to crash, resulting in a denial of service, or possibly execute
arbitrary code. (CVE-2016-8618)&lt;/p&gt;
&lt;p&gt;It was discovered that curl incorrect handled memory when performing
Kerberos authentication. A remote attacker could pos…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-3123-1</guid>
    </item>
  </channel>
</rss>
