<?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>Mon, 05 Oct 2026 15:01:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-78619 — Punk::Plugin::TOTP versions before 0.05 for Perl accept another account's recovery code at the two-factor challenge bec…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-78619</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Punk-TOTP&lt;/p&gt;
&lt;p&gt;Punk::Plugin::TOTP versions before 0.05 for Perl accept another account&amp;#39;s recovery code at the two-factor challenge because totp_use_recovery compares user identifiers numerically.&lt;/p&gt;
&lt;p&gt;The helper searches the recovery model for the submitted code&amp;#39;s digest alone, across every user&amp;#39;s rows, so the ownership test that follows is the only thing binding a code to the account it was issued to. That test compares the row&amp;#39;s user_id with the challenged user&amp;#39;s id through Perl&amp;#39;s integer coercion, and an identifier with no leading digits coerces to zero, so any two of them compare equal. User models keyed on a username, an email address or a UUID hit that case, and a numeric key compares as intended.&lt;/p&gt;
&lt;p&gt;The challenge route feeds a submitted value to the helper once TOTP verification fails, so an attacker who knows a victim&amp;#39;s password and holds a recovery code of their own passes the victim&amp;#39;s second factor.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Punk-TOTP&lt;/p&gt;
&lt;p&gt;Punk::Plugin::TOTP versions before 0.05 for Perl accept another account&amp;#39;s recovery code at the two-factor challenge because totp_use_recovery compares user identifiers numerically.&lt;/p&gt;
&lt;p&gt;The helper searches the recovery model for the submitted code&amp;#39;s digest alone, across every user&amp;#39;s rows, so the ownership test that follows is the only thing binding a code to the account it was issued to. That test compares the row&amp;#39;s user_id with the challenged user&amp;#39;s id through Perl&amp;#39;s integer coercion, and an identifier with no leading digits coerces to zero, so any two of them compare equal. User models keyed on a username, an email address or a UUID hit that case, and a numeric key compares as intended.&lt;/p&gt;
&lt;p&gt;The challenge route feeds a submitted value to the helper once TOTP verification fails, so an attacker who knows a victim&amp;#39;s password and holds a recovery code of their own passes the victim&amp;#39;s second factor.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-78619</guid>
    </item>
  </channel>
</rss>
