The Azure Active Directory (AAD) authentication implementation contained multiple weaknesses in its OAuth 2.0 authorization flow that could allow attackers to bypass important security guarantees provided by the protocol. The application used the PHP session identifier (session_id()) as the OAuth state parameter. Because session identifiers are long-lived authentication credentials, exposing them in OAuth redirect URLs could leak valid session tokens through browser history, HTTP Referer headers, reverse proxies, access logs, or third-party infrastructure involved in the authentication flow. If obtained by an attacker, the leaked session identifier could potentially be used for session hijacking. Additionally, the implementation did not regenerate the session identifier after successful authentication, leaving authenticated sessions susceptible to session fixation attacks where an attacker forces a victim to use a known session identifier before login and later reuses that identifier after authentication. The OAuth state value was also not implemented as a dedicated, single-use nonce. This weakened CSRF protections and increased the risk of replay attacks against the OAuth callback process. The authentication flow further failed to enforce HTTPS for the configured OAuth redirect URI. If a non-HTTPS redirect URI was used, OAuth authorization codes and access tokens could traverse the network in plaintext, exposing sensitive credentials to network attackers. Finally, OAuth error responses containing attacker-controlled GET parameters were logged verbatim. An attacker could inject control characters or crafted log content, leading to log forging, log injection, or corruption of audit records. The fix introduces: * A dedicated cryptographically random OAuth state value. * Single-use state validation and invalidation. * Constant-time state comparison using hash_equals(). * Session identifier rotation after successful authentication. * Enforcement of HTTPS-only redirect URIs. * Sanitized and length-limited logging of OAuth error parameters. AAD Authentication Plugin (OAuth 2.0 / Azure Active Directory integration)
The application used the PHP session ID (session_id()) as the OAuth state parameter, leading to exposure of long-lived session tokens in URLs, Referer headers, access logs, and intermediary infrastructure. After successful authentication, the session ID was not regenerated, enabling session fixation attacks — an attacker could pre-impose a known session ID on the victim and subsequently hijack it. The OAuth state value was not a one-time nonce, weakening CSRF protection and replay attacks on the OAuth callback. The implementation also did not enforce HTTPS for the redirect URI, exposing authorization codes and access tokens to interception in network traffic in plain text. Additionally, OAuth errors containing attacker-controlled GET parameters were logged without sanitization, enabling log injection and audit record forgery.
An attacker can hijack the session of an authenticated user (session hijacking or session fixation), bypass CSRF protection, intercept OAuth tokens transmitted over an unencrypted channel, and forge or corrupt audit logs by injecting controlled data.
Apply the patch available in the vendor references (commit 146bc40ad6e10a44f01e8ed62d5f7bc9c06cc4fa in the MISP GitHub repository). The patch introduces a cryptographically random one-time nonce as OAuth state, session ID rotation after authentication, constant-time state comparison (hash_equals()), enforcement of HTTPS for redirect URI, and sanitization of logged OAuth error parameters.
Misp-Project MISP with AAD authentication plugin enabled (OAuth 2.0 / Azure Active Directory); specific versions indicated in vendor references
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XMisp Project Misp
APPMisp-Project< 2.5.42
Related vulnerabilities
MISP: błędna kontrola dostępu w masowym usuwaniu obiektów (CWE-862)
MISP: RCE przez złośliwy plik konfiguracyjny rdkafka (CWE-829)
SQL Injection w MISP — manipulacja parametrami sortowania zapytań
MISP: Nieprawidłowa weryfikacja przesyłanego logo organizacji
MISP: Nieprawidłowa walidacja uploadu pliku umożliwia RCE