Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition to observe victim login
-
DeliveryCapture valid TOTP code
-
ExploitReplay code within 30s window
-
ExecutionComplete second authenticated session
-
ImpactAccess threat-intel data and admin functions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Replay attack prevention
|
| Exploitation Conditions | Exploitation requires ALL of the following to align: (1) the target MISP user has TOTP-based two-factor authentication enabled (the flaw only matters when this hardening feature is active); (2) the attacker is positioned to observe or intercept the live TOTP code during a genuine login - e.g., network-level interception/MITM, shoulder-surfing, or a compromised client endpoint - and in practice must also obtain the first-factor credentials to complete the login; and (3) the replay occurs within the single TOTP validity period (typically ~30 seconds). These interception and tight-timing requirements are the key limiters: the flaw is not remotely exploitable against an arbitrary user without an interception vantage point, so despite PR:N it is not a drive-by unauthenticated attack. Affected in all versions before v2.5.48; fixed by recording consumed TOTP steps in Redis. |
| Impact | This is a CWE-294 capture-replay weakness in MISP's TOTP second-factor verification: the login flow did not mark a TOTP time-step as consumed, so a captured code stayed valid for its full ~30s window and could be replayed to log in a second session. The vendor CVSS 4.0 score of 9.3 (Critical) is driven by AV:N/AC:L/AT:N/PR:N/UI:N and VC:H/VI:H, but that rating materially overstates real-world risk because it ignores the explicit preconditions in the description: the attacker must already be positioned to intercept a valid code (network MITM, shoulder-surfing, or a compromised client) AND act within the short validity window. Those are genuine attack requirements, so AT:N (and AC:L) are optimistic - an interception-plus-timing precondition is better modeled as AC:H/AT:P, which is why my independent 3.1 score lands near 8.0 rather than 9.3. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the supplied data, so this is not evidence of active or automatable exploitation; it is a defense-in-depth weakening of 2FA that requires an attacker who can already observe traffic/credentials. Net: a legitimate issue worth patching (a vendor fix exists), but a conditional, position-dependent flaw rather than a wormable mass-exploitation priority despite the Critical headline number. |
| Exploit ScenarioDerived | An attacker who can observe a target user's MISP login - e.g., via a man-in-the-middle position on the network, shoulder-surfing, or malware on the user's client - captures the 6-digit TOTP code as it is submitted. Within the same ~30-second validity window the attacker replays that code (alongside the user's first-factor credentials) to the MISP login endpoint and authenticates a second, parallel session as the victim, gaining access to the threat-intelligence data and any administrative functions that account holds. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
MISP (Malware Information Sharing Platform) versions before v2.5.48 accept the same TOTP one-time code more than once, allowing a captured second-factor code to be replayed to open an additional authenticated session. The flaw is a CWE-294 capture-replay weakness: the login flow never recorded that a given TOTP time-step had already been consumed, so a code remained usable for its entire ~30-second validity window. Exploitation is conditional rather than drive-by - the targeted user must have TOTP enabled, the attacker must be able to observe or intercept the live code (network interception, shoulder surfing, or a compromised client) and in practice also hold the first-factor credentials, and the replay must land inside the same TOTP period; the vendor has released a fix in v2.5.48, and no public exploit code has been identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to MISP v2.5.48 or later, which contains commit a020fa47b (https://github.com/MISP/MISP/commit/a020fa47b); the fix adds a Redis-backed, NX-guarded per-step claim ('misp:otp:totp_used:<userId>:<step>', expiring after three TOTP periods) so each TOTP time-step can be redeemed only once. Because the patch depends on RedisTool, confirm Redis is reachable and correctly configured before deploying, as the single-use enforcement is enforced through a Redis set operation with the NX flag; if Redis is degraded the claim may fail and login verification could behave unexpectedly. Until upgrading is possible, the practical compensating controls are to reduce the attack surface rather than fully eliminate the replay: enforce TLS/HSTS across the entire MISP interface (including any reverse proxy or API paths) to block network-level interception of the code, mandate strong unique first-factor credentials and rate-limit or lock out repeated failed OTP submissions, and treat client endpoints that access MISP as high-value - since a compromised client or shoulder surfing defeats TLS-only mitigations. Disabling TOTP entirely is not a recommended workaround because it removes a critical second factor; if administrators temporarily shorten the TOTP period it narrows but does not close the replay window and can increase user lockouts. After patching, rotate TOTP enrolments for any account suspected of code interception, since a captured shared secret is not invalidated by this fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability class is CWE-294 (Authentication Bypass by Capture-replay). MISP's second-factor login flow is implemented in app/Controller/UsersController.php, where the otp() action validated the submitted code with \OTPHP\TOTP::verify(). Standard TOTP (RFC 6238) derives a code from the shared secret and the current time-step (typically 30 seconds); by design a correct code matches for the whole step, but a correct implementation must additionally mark that step as spent so it cannot authorize a second authentication. MISP did not persist any consumed-step state, so any observer of a valid code could resubmit it within the window and be granted a new session for the same user. The upstream fix (commit a020fa47b) passes the current timestamp explicitly into verify() and then calls a new private helper __claimTotpStep(), which computes the step index as intdiv($timestamp - $totp->getEpoch(), $totp->getPeriod()) and writes a Redis key of the form 'misp:otp:totp_used:<userId>:<step>' using set() with the NX and EX options, expiring the marker after three TOTP periods. That NX-based single-use claim makes each TOTP step redeemable exactly once, which is the standard replay-resistant construction for time-based OTP. The affected CPE is cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*, and the vulnerability spans every release before v2.5.48. Note that the flaw only manifests when TOTP two-factor authentication is actually enabled for the target account; deployments without TOTP are unaffected by this specific issue.
Know when Misp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
AC:H because the attacker must intercept a live code and replay within the ~30s window; PR:N since the flaw is in the pre-auth factor itself; C:H/I:H for full account takeover, A:N as availability is unaffected.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
DescriptionCVE.org
MISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a valid one-time code to be accepted more than once within its time-based validity window.
The issue exists in the user login flow where a TOTP code is verified as a second authentication factor. Because the system did not record whether a given TOTP period had already been consumed, the same code remained valid for its entire time window (typically 30 seconds). An attacker who captures a legitimate code during a user's login could replay it to authenticate a second session as that user.
Preconditions:
- The target user has TOTP-based two-factor authentication enabled.
- The attacker is in a position to observe or intercept the TOTP code during a legitimate login (e.g., network-level interception, shoulder surfing, or a compromised client).
- The replay must occur within the TOTP validity period.
Security impact:
- Unauthorized account access by replaying a captured one-time code.
- Potential compromise of threat-intelligence data and administrative functions accessible to the targeted user.
Affected versions: <v2.5.48.
Articles & Coverage 1
Executive ViewAI
MISP, the threat intelligence sharing platform many security teams use to exchange indicators with peers and sector partners, is affected in all versions prior to v2.5.48 by a multi-factor authentication replay flaw rated CVSS 9.3. Because a captured one-time passcode can be reused within its roughly 30-second validity window to open an additional authenticated session, MFA cannot be relied on as a control protecting the instance and the sensitive indicator data and contributor identities it holds until the upgrade is applied. Exploitation is conditional - the attacker must already hold valid first-factor credentials and intercept a live code - so exposure is concentrated in environments where credentials are phishable or endpoints are compromised rather than in opportunistic internet-wide scanning.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
An issue was discovered in MISP 2.4.9x before 2.4.99. Rated high severity (CVSS 8.8), this vulnerability is remotely exp
An issue was discovered in MISP before 2.4.158. Rated critical severity (CVSS 9.8), this vulnerability is remotely explo
app/Controller/Component/IndexFilterComponent.php in MISP before 2.4.167 mishandles ordered_url_params and additional_de
SQL injection in MISP threat intelligence platform versions prior to 2.5.37 allows remote unauthenticated attackers to m
An issue was discovered in MISP before 2.4.158. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitab
MISP 2.4.172 mishandles different certificate file extensions in server sync. Rated high severity (CVSS 7.5), this vulne
In MISP before 2.4.148, app/Lib/Export/OpendataExport.php mishandles parameter data that is used in a shell_exec call. R
An issue was discovered in app/Controller/UsersController.php in MISP 2.4.92. Rated critical severity (CVSS 9.8), this v
An issue was discovered in MISP 2.4.128. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
MISP before 2.4.135 lacks an ACL check, related to app/Controller/GalaxyElementsController.php and app/Model/GalaxyEleme
app/View/Elements/genericElements/IndexTable/Fields/generic_field.ctp in MISP 2.4.144 does not sanitize certain data rel
MISP 2.4.148, in certain configurations, allows SQL injection via the app/Model/Log.php $conditions['org'] value. Rated
EUVD-2026-90550
GHSA-2hxj-rrwr-5g5v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB