Authentication Bypass in github.com/russellhaering/gosaml2
### Impact Given a valid SAML Response, it may be possible for an attacker to mutate the XML document in such a way that gosaml2 will trust a different portion of the document than was signed. Depending on the implementation of the Service Provider 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. ### Patches Service Providers utilizing gosaml2 should upgrade to v0.6.0 or greater.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-29509US | medium5.6 | — | ||
The encoding/xml package in Go (all versions) does not correctly preserve the semantics of attribute namespace prefixes during tokenization round-trips, which allows an attacker to… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.mdWEB
- https://github.com/russellhaering/gosaml2/commit/42606dafba60c58c458f14f75c4c230459672ab9WEB
- https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fggWEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-29509ADVISORY
- https://pkg.go.dev/vuln/GO-2021-0060WEB
- https://security.netapp.com/advisory/ntap-20210129-0006WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan