Signature Validation Bypass
Published 24 May 2021 · Updated 5 Oct 2021
Is your project on an affected github.com/russellhaering/gosaml2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.5.0
- Fixed in
- 0.5.0
go get github.com/russellhaering/gosaml2@v0.5.0Details
Impact
Given a valid SAML Response, an attacker can potentially modify the document, bypassing signature validation in order to pass off the altered document as a signed one.
This enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the identity provider, or full authentication bypass if an external attacker can obtain an expired, signed SAML Response.
Patches
A patch is available, users of gosaml2 should upgrade to v0.5.0 or higher.
References
See the underlying advisory on goxmldsig for more details.
Is GHSA-5684-g483-2249 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/russellhaering/gosaml2, and gives you the command that fixes it.
More advisories for github.com/russellhaering/gosaml2
- HighCVE-2026-128073gosaml2: Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue · 19 Nov 2026
- LowGO-2026-4760CBC Padding Panic — Unauthenticated Process Crash in github.com/russellhaering/gosaml2 · 27 Mar 2026
- LowGO-2026-4764Unsigned SAML LogoutRequest Acceptance in gosaml2 in github.com/russellhaering/gosaml2 · 27 Mar 2026
- HighGHSA-pcgw-qcv5-h8chUnsigned SAML LogoutRequest Acceptance in gosaml2 · 18 Mar 2026
- HighGHSA-hwqm-qvj9-4jr2gosaml2 CBC Padding Panic — Unauthenticated Process Crash · 18 Mar 2026
- LowCVE-2023-26483Denial of service via deflate decompression bomb in github.com/russellhaering/gosaml2 · 3 Mar 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.