<?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://db.gcve.eu</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>Thu, 05 Nov 2026 12:39:06 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2024-0442 — Dump Undefined Memory by `JitDumpFile`</title>
      <link>https://db.gcve.eu/vuln/rustsec-2024-0442</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime-jit-debug&lt;/p&gt;
&lt;p&gt;The unsound function `dump_code_load_record` uses `from_raw_parts` to directly convert 
the pointer `addr` and `len` into a slice without any validation and that memory block 
would be dumped.&lt;/p&gt;
&lt;p&gt;Thus, the &amp;#39;safe&amp;#39; function dump_code_load_record is actually &amp;#39;unsafe&amp;#39; since it requires 
the caller to guarantee that the addr is valid and len must not overflow.
Otherwise, the function could dump the memory into file illegally, causing memory leak.&lt;/p&gt;
&lt;p&gt;&amp;gt; **Note**: this is an internal-only crate in the Wasmtime project not intended for
external use and is more strongly signaled nowadays as of
[bytecodealliance/wasmtime#10963](https://github.com/bytecodealliance/wasmtime/pull/10963).
Please open an issue in Wasmtime if you&amp;#39;re using this crate directly.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime-jit-debug&lt;/p&gt;
&lt;p&gt;The unsound function `dump_code_load_record` uses `from_raw_parts` to directly convert 
the pointer `addr` and `len` into a slice without any validation and that memory block 
would be dumped.&lt;/p&gt;
&lt;p&gt;Thus, the &amp;#39;safe&amp;#39; function dump_code_load_record is actually &amp;#39;unsafe&amp;#39; since it requires 
the caller to guarantee that the addr is valid and len must not overflow.
Otherwise, the function could dump the memory into file illegally, causing memory leak.&lt;/p&gt;
&lt;p&gt;&amp;gt; **Note**: this is an internal-only crate in the Wasmtime project not intended for
external use and is more strongly signaled nowadays as of
[bytecodealliance/wasmtime#10963](https://github.com/bytecodealliance/wasmtime/pull/10963).
Please open an issue in Wasmtime if you&amp;#39;re using this crate directly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2024-0442</guid>
    </item>
  </channel>
</rss>
