Technical impact
gosaml2, a Pure Go SAML 2.0 library, contains a flaw that allows an unauthenticated attacker to provoke a panic by sending a crafted EncryptedAssertion. The library performs decryption of the assertion before validating its signature, and the decryption routine slices the ciphertext without checking the nonce or initialization‑vector length. A CipherValue shorter than the required 12‑byte AES‑GCM nonce, or an empty AES‑CBC CipherValue, triggers a slice‑bounds panic. The panic may terminate the request goroutine or the entire service process, resulting in a denial of service. The weakness is reflected in CWE‑20 (Input Validation) and CWE‑248 (Unexpected ≤).
Affected Systems
The vulnerability affects any deployment that incorporates gosaml2 versions earlier than 0.12.0. This includes codebases that rely on the library for processing SAML assertions in their identity‑provider or service‑provider roles.*
Risk and Exploitability
The CVSS score of 7.5 categorizes this issue as high severity. While the EPSS score is not available, there is no indication that this flaw has been exploited in the wild, and it is not listed in the CISA KEV catalog. The attack can be carried out over the network without needing legitimate identity‑provider signatures; the attacker merely needs the service provider's public certificate to wrap a symmetric key. Consequently, the likely attack vector is a crafted SAML response sent to a service that uses gosaml2 to validate assertions. The attacker can repeatedly trigger the panic to disrupt availability.