You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement. In deployments configured with LdapAuth.mixedAuth=true and Security.require_otp=true, users authenticated through an authentication plugin, such as LDAP, may have their authenticated session established during the application beforeFilter phase before the normal login flow enforces the OTP challenge.
As a result, an attacker with valid primary authentication credentials could bypass the required OTP step by authenticating through the plugin-backed login flow and then directly accessing another application URL instead of completing the OTP verification page. This allows access to the application as the affected user without providing a valid TOTP, HOTP, or email OTP code.
The issue affects configurations where plugin-based authentication is enabled and OTP is expected to be mandatory. The fix ensures that OTP requirements are checked immediately after plugin authentication and before the user session is established, redirecting users to the appropriate OTP challenge when required.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: misp, Description: Una vulnerabilidad de omisión de autenticación existe en MISP cuando la autenticación mixta LDAP está habilitada con la aplicación de OTP. En implementaciones configuradas con LdapAuth.mixedAuth=true y Security.require_otp=true, los usuarios autenticados a través de un plugin de autenticación, como LDAP, pueden tener su sesión autenticada establecida durante la fase beforeFilter de la aplicación antes de que el flujo de inicio de sesión normal aplique el desafío OTP.
Como resultado, un atacante con credenciales de autenticación primaria válidas podría omitir el paso OTP requerido autenticándose a través del flujo de inicio de sesión respaldado por el plugin y luego accediendo directamente a otra URL de la aplicación en lugar de completar la página de verificación OTP. Esto permite el acceso a la aplicación como el usuario afectado sin proporcionar un código TOTP, HOTP o OTP por correo electrónico válido.
El problema afecta a las configuraciones donde la autenticación basada en plugin está habilitada y se espera que el OTP sea obligatorio. La solución garantiza que los requisitos de OTP se verifiquen inmediatamente después de la autenticación del plugin y antes de que se establezca la sesión del usuario, redirigiendo a los usuarios al desafío OTP apropiado cuando sea necesario.
CPE Deprecation Remap by NIST6/22/2026 3:23:18 PM
Action
Type
Old Value
New Value
Changed
CPE Configuration
OR
*cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* versions from (excluding) 2.5.39
OR
*cpe:2.3:a:misp-project:misp:*:*:*:*:*:*:*:* versions from (excluding) 2.5.39
An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement. In deployments configured with LdapAuth.mixedAuth=true and Security.require_otp=true, users authenticated through an authentication plugin, such as LDAP, may have their authenticated session established during the application beforeFilter phase before the normal login flow enforces the OTP challenge.
As a result, an attacker with valid primary authentication credentials could bypass the required OTP step by authenticating through the plugin-backed login flow and then directly accessing another application URL instead of completing the OTP verification page. This allows access to the application as the affected user without providing a valid TOTP, HOTP, or email OTP code.
The issue affects configurations where plugin-based authentication is enabled and OTP is expected to be mandatory. The fix ensures that OTP requirements are checked immediately after plugin authentication and before the user session is established, redirecting users to the appropriate OTP challenge when required.