<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T05:17:13.295303+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2021-28030</id>
    <title>CVE-2021-28030</title>
    <updated>2026-10-15T05:17:13.329599+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-28030"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2021-0029</id>
    <title>RUSTSEC-2021-0029 — Tape::take_bytes exposes uninitialized memory to a user-provided Read</title>
    <updated>2026-10-15T05:17:13.329650+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: truetype</p>
<p>Affected versions of this crate passed an unininitialized buffer to a
user-provided `Read` instance in `Tape::take_bytes`.</p>
<p>This can result in safe `Read` implementations reading from the uninitialized
buffer leading to undefined behavior.</p>
<p>The flaw was corrected in commit `1f2dc7f37dd` by removing the unsafe block
and zero-initializing the buffer.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2021-0029"/>
  </entry>
</feed>
