<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T08:07:29.074682+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cnvd-2024-35173</id>
    <title>cnvd-2024-35173</title>
    <updated>2026-10-07T08:07:29.481186+00:00</updated>
    <content>cnvd-2024-35173</content>
    <link href="https://vulnerability.circl.lu/vuln/cnvd-2024-35173"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2024-41800</id>
    <title>fkie_cve-2024-41800</title>
    <updated>2026-10-07T08:07:29.481279+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Craft is a content management system (CMS). Craft CMS 5 allows reuse of TOTP tokens multiple times within the validity period. An attacker is able to re-submit a valid TOTP token to establish an authenticated session. This requires that the attacker has knowledge of the victim's credentials. This has been patched in Craft 5.2.3.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2024-41800"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-wmx7-pw49-88jx</id>
    <title>GHSA-wmx7-pw49-88jx — Craft CMS Allows TOTP Token To Stay Valid After Use</title>
    <updated>2026-10-07T08:07:29.481342+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: craftcms/cms</p>
<p>Craft CMS 5 allows reuse of TOTP tokens multiple times within the validity period.</p>
<p>### Impact</p>
<p>An attacker is able to re-submit a valid TOTP token to establish an authenticated session. This requires that the attacker has knowledge of the victim's credentials.</p>
<p>A TOTP token can be used multiple times to establish an authenticated session.
[RFC 6238](https://www.rfc-editor.org/rfc/rfc6238) insists that an OTP must not be used more than once.</p>
<p>&gt; The verifier MUST NOT accept the second attempt of the OTP after the successful validation has been issued for the first OTP, which ensures one-time only use of an OTP.</p>
<p>The OWASP Application Security Verification Standard v4.0.3 (ASVS) [reiterates
this property with requirement 2.8.4](https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x11-V2-Authentication.md#v28-one-time-verifier).</p>
<p>&gt; Verify that time-based OTP can be used only once within the validity period.</p>
<p>It should also be noted that the validity period of an TOTP token is 2 minutes. This makes a successful brute force attack more likely, since the four tokens are valid at the same time.</p>
<p>### Patches</p>
<p>This has been patched in Craft 5.2.3.</p>
<p>References:</p>
<p>https://github.com/sbaresearch/advisories/tree/public/2024/SBA-ADV 2024061701_CraftCMS_TOTP_Valid_After_Use</p>
<p>https://github.com/craftcms/cms/releases/tag/5.2.3</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-wmx7-pw49-88jx"/>
  </entry>
</feed>
