<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-11T19:39:00.525766+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/rustsec-2026-0490</id>
    <title>RUSTSEC-2026-0490 — Zone file lexer panics on a token of 4096 or more characters</title>
    <updated>2026-11-11T19:39:00.541813+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: hickory-proto</p>
<p>The zone file lexer read each token in a loop capped at 4,096 iterations, with an `assert!` on the loop counter as a safety bound. A single token long enough to reach that bound, for example a very long name or character string in a zone file, triggered the assertion and the parser panicked instead of returning the token or an error.</p>
<p>Code that parses zone files from an untrusted source can be made to panic, which is a denial of service.</p>
<p>The fix removes the iteration bound, so the lexer ends only when it reaches the end of a token or an error. It is in 0.26.2.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/rustsec-2026-0490"/>
  </entry>
</feed>
