<?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, 24 Oct 2026 20:32:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-28305</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-28305</link>
      <description>&lt;p&gt;An issue was discovered in the diesel crate before 1.4.6 for Rust. There is a use-after-free in the SQLite backend because the semantics of sqlite3_column_name are not followed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the diesel crate before 1.4.6 for Rust. There is a use-after-free in the SQLite backend because the semantics of sqlite3_column_name are not followed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-28305</guid>
    </item>
    <item>
      <title>RUSTSEC-2021-0037 — Fix a use-after-free bug in diesels Sqlite backend</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2021-0037</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: diesel&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve misused `sqlite3_column_name`. The
[SQLite](https://www.sqlite.org/c3ref/column_name.html) documentation
states that the following:&lt;/p&gt;
&lt;p&gt;&amp;gt; The returned string pointer is valid until either the prepared statement
&amp;gt; is destroyed by sqlite3_finalize() or until the statement is automatically
&amp;gt; reprepared by the first call to sqlite3_step() for a particular
&amp;gt; run or until the next call to sqlite3_column_name()
&amp;gt; or sqlite3_column_name16() on the same column.&lt;/p&gt;
&lt;p&gt;As part of our `query_by_name` infrastructure we&amp;#39;ve first received all
field names for the prepared statement and stored them as string slices
for later use. After that we called `sqlite3_step()` for the first time,
which invalids the pointer and therefore the stored string slice.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: diesel&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve misused `sqlite3_column_name`. The
[SQLite](https://www.sqlite.org/c3ref/column_name.html) documentation
states that the following:&lt;/p&gt;
&lt;p&gt;&amp;gt; The returned string pointer is valid until either the prepared statement
&amp;gt; is destroyed by sqlite3_finalize() or until the statement is automatically
&amp;gt; reprepared by the first call to sqlite3_step() for a particular
&amp;gt; run or until the next call to sqlite3_column_name()
&amp;gt; or sqlite3_column_name16() on the same column.&lt;/p&gt;
&lt;p&gt;As part of our `query_by_name` infrastructure we&amp;#39;ve first received all
field names for the prepared statement and stored them as string slices
for later use. After that we called `sqlite3_step()` for the first time,
which invalids the pointer and therefore the stored string slice.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2021-0037</guid>
    </item>
  </channel>
</rss>
