CVE-2026-56425
- Source
- https://cve.org/CVERecord?id=CVE-2026-56425
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-56425.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-56425
- Published
- 2026-06-22T12:25:00Z
- Modified
- 2026-08-12T03:51:11Z
- Severity
-
- 9.3 (Critical) CVSS_V4 - 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 CVSS Calculator
- Summary
- MISP AAD authentication plugin - Improper OAuth State Handling, Missing Session Rotation, Insecure Redirect URI Validation, and Log Injection
- Details
-
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)
- Database specific
{ "cna_assigner": "CIRCL", "cwe_ids": [ "CWE-384" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/56xxx/CVE-2026-56425.json" }- References
Affected packages
Git / github.com/misp/misp
Affected ranges
- Type
- GIT
- Repo
- https://github.com/misp/misp
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixedFixed
- Database specific
-
Show details
{ "cpe": "cpe:2.3:a:misp-project:misp:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "2.5.42" } ], "source": [ "CPE_RANGE", "REFERENCES" ] }