gosaml2 flaw lets unauthenticated attackers crash service providers
- gosaml2
- SAML
- AES-GCM
- panic

A crafted SAML response triggers a panic in AES-GCM processing
Affected versions up to 0.11.0 require update to 0.12.0
Attack does not require valid identity provider signatures
The gosaml2 project has disclosed an unauthenticated denial-of-service vulnerability in its Go library for SAML, a standard used for exchanging authentication data. A crafted response can crash a service provider when it processes an encrypted assertion with AES-GCM metadata and a ciphertext value shorter than the 12-byte nonce required by that encryption mode.
The GitHub advisory says the library panics with a slice-bounds error before it completes validation or checks a signature. The panic propagates and terminates the affected goroutine because the library does not recover from it; an attacker does not need a valid identity-provider relationship or signature to trigger the crash.
The flaw affects gosaml2 versions through 0.11.0 and is separate from an earlier issue in the library’s AES-CBC decryption path. The advisory identifies version 0.12.0 as patched.
Key terms explained
- denial-of-service
A denial-of-service attack aims to make a service or system unusable for legitimate users. This is often achieved by overwhelming the system with requests or exploiting vulnerabilities to cause a crash.
Think of it this way. It is like a group of people crowding the entrance of a store so that actual customers cannot get inside to shop.




