<?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>Sun, 15 Nov 2026 04:20:25 +0000</lastBuildDate>
    <item>
      <title>GHSA-4q52-849c-cv9p</title>
      <link>https://db.gcve.eu/vuln/ghsa-4q52-849c-cv9p</link>
      <description>&lt;p&gt;JSON::XS versions from 4.0_00 before 4.05 for Perl corrupt the incremental buffer length by chopping past its end in incr_skip after a top-level number.&lt;/p&gt;
&lt;p&gt;The incremental parser scans any run of digits, signs, dots and exponent markers as one number, but the decoder stops at the end of a valid number, so the parser keeps an offset into bytes it has not decoded. It then empties the buffer without clearing those bytes, and a later incr_parse call without new input reads them again and moves the offset past the end of the buffer. incr_skip, the documented recovery after an error, removes that many bytes and the buffer length wraps.&lt;/p&gt;
&lt;p&gt;A peer sending input such as &amp;#34;1-2&amp;#34; to an incr_parse consumer can make the next read of incr_text exit the process through perl&amp;#39;s uncatchable out-of-memory path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;JSON::XS versions from 4.0_00 before 4.05 for Perl corrupt the incremental buffer length by chopping past its end in incr_skip after a top-level number.&lt;/p&gt;
&lt;p&gt;The incremental parser scans any run of digits, signs, dots and exponent markers as one number, but the decoder stops at the end of a valid number, so the parser keeps an offset into bytes it has not decoded. It then empties the buffer without clearing those bytes, and a later incr_parse call without new input reads them again and moves the offset past the end of the buffer. incr_skip, the documented recovery after an error, removes that many bytes and the buffer length wraps.&lt;/p&gt;
&lt;p&gt;A peer sending input such as &amp;#34;1-2&amp;#34; to an incr_parse consumer can make the next read of incr_text exit the process through perl&amp;#39;s uncatchable out-of-memory path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-4q52-849c-cv9p</guid>
    </item>
  </channel>
</rss>
