<?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>Wed, 07 Oct 2026 02:02:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16138</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2019-16138</link>
      <description>&lt;p&gt;An issue was discovered in the image crate before 0.21.3 for Rust, affecting the HDR image format decoder. Vec::set_len is called on an uninitialized vector, leading to a use-after-free and arbitrary code execution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the image crate before 0.21.3 for Rust, affecting the HDR image format decoder. Vec::set_len is called on an uninitialized vector, leading to a use-after-free and arbitrary code execution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2019-16138</guid>
    </item>
    <item>
      <title>GHSA-m2pf-hprp-3vqm — Use after free in image</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m2pf-hprp-3vqm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: image&lt;/p&gt;
&lt;p&gt;Affected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.&lt;/p&gt;
&lt;p&gt;This could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.&lt;/p&gt;
&lt;p&gt;Two different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.&lt;/p&gt;
&lt;p&gt;Starting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: image&lt;/p&gt;
&lt;p&gt;Affected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.&lt;/p&gt;
&lt;p&gt;This could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.&lt;/p&gt;
&lt;p&gt;Two different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.&lt;/p&gt;
&lt;p&gt;Starting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m2pf-hprp-3vqm</guid>
    </item>
  </channel>
</rss>
