Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-42615: CWE-307 Improper Restriction of Excessive Authentication Attempts in CIRCL Vulnerability-Lookup

0
High
VulnerabilityCVE-2025-42615cvecve-2025-42615cwe-307
Published: Mon Dec 08 2025 (12/08/2025, 12:01:05 UTC)
Source: CVE Database V5
Vendor/Project: CIRCL
Product: Vulnerability-Lookup

Description

In affected versions, vulnerability-lookup did not track or limit failed One-Time Password (OTP) attempts during Two-Factor Authentication (2FA) verification. An attacker who already knew or guessed a valid username and password could submit an arbitrary number of OTP codes without causing the account to be locked or generating any specific alert for administrators. This lack of rate-limiting and lockout on OTP failures significantly lowers the cost of online brute-force attacks against 2FA codes and increases the risk of successful account takeover, especially if OTP entropy is reduced (e.g. short numeric codes, user reuse, or predictable tokens). Additionally, administrators had no direct visibility into accounts experiencing repeated 2FA failures, making targeted attacks harder to detect and investigate. The patch introduces a persistent failed_otp_attempts counter on user accounts, locks the user after 5 invalid OTP submissions, resets the counter on successful verification, and surfaces failed 2FA attempts in the admin user list. This enforces an account lockout policy for OTP brute-force attempts and improves monitoring capabilities for suspicious 2FA activity.This issue affects Vulnerability-Lookup: before 2.18.0.

AI-Powered Analysis

AILast updated: 12/08/2025, 12:27:14 UTC

Technical Analysis

CVE-2025-42615 affects CIRCL's Vulnerability-Lookup software versions before 2.18.0 by failing to enforce restrictions on the number of failed OTP attempts during 2FA verification. Specifically, the system does not track or limit failed OTP submissions, allowing an attacker who has already compromised or guessed valid username and password credentials to submit unlimited OTP codes without triggering account lockout or administrative alerts. This flaw significantly lowers the cost and effort required for online brute-force attacks against 2FA, undermining the security benefits of multi-factor authentication. The vulnerability is particularly critical when OTP entropy is low, such as short numeric codes or predictable tokens, or when users reuse OTP secrets. Additionally, administrators lack visibility into repeated failed OTP attempts, making detection and response to targeted attacks difficult. The vulnerability is classified under CWE-307 (Improper Restriction of Excessive Authentication Attempts). The patch for this issue introduces a persistent counter for failed OTP attempts, locks accounts after 5 invalid OTP submissions, resets the counter upon successful verification, and surfaces failed 2FA attempts in the admin user interface to improve monitoring and response. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required beyond valid credentials, user interaction required, high impact on confidentiality, no impact on integrity or availability, and high scope and security requirements. No known exploits have been reported in the wild as of the publication date.

Potential Impact

For European organizations using CIRCL's Vulnerability-Lookup, this vulnerability poses a significant risk of account takeover through brute-force attacks on 2FA mechanisms. Successful exploitation could lead to unauthorized access to sensitive vulnerability data, potentially exposing internal security posture and enabling further attacks. The lack of lockout and alerting mechanisms increases the likelihood of stealthy attacks going unnoticed, complicating incident detection and response. Organizations relying on short or predictable OTP codes are especially vulnerable. The compromise of privileged accounts could lead to broader network compromise or data breaches. Given the critical role of vulnerability management tools in security operations, exploitation could disrupt security workflows and erode trust in security controls. The impact is heightened in sectors with stringent regulatory requirements for data protection and incident reporting, such as finance, healthcare, and critical infrastructure within Europe.

Mitigation Recommendations

European organizations should immediately upgrade CIRCL Vulnerability-Lookup to version 2.18.0 or later, which includes the patch enforcing OTP attempt limits and account lockouts. Until patching is possible, organizations should implement compensating controls such as monitoring authentication logs for repeated failed OTP attempts and setting up alerts for suspicious 2FA activity. Enforce strong OTP policies with high entropy tokens and discourage OTP reuse. Consider integrating additional anomaly detection systems to identify brute-force patterns. Limit access to the Vulnerability-Lookup system to trusted networks and use network-level protections such as IP whitelisting or VPNs. Conduct regular audits of user accounts and 2FA configurations to ensure compliance with security policies. Educate administrators on the importance of monitoring failed 2FA attempts and responding promptly to suspicious activity. Finally, review and enhance incident response plans to address potential account takeover scenarios involving this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
ENISA
Date Reserved
2025-04-16T12:34:02.866Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6936c3245f72f49d1523dfe6

Added to database: 12/8/2025, 12:23:00 PM

Last enriched: 12/8/2025, 12:27:14 PM

Last updated: 12/8/2025, 5:36:06 PM

Views: 23

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats