Skip to content

Authentication Bypass in github.com/russellhaering/gosaml2

Critical severity GitHub Reviewed Published Dec 14, 2020 in russellhaering/gosaml2 • Updated Feb 16, 2023

Package

gomod github.com/russellhaering/gosaml2 (Go)

Affected versions

< 0.6.0

Patched versions

0.6.0

Description

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.

References

@russellhaering russellhaering published to russellhaering/gosaml2 Dec 14, 2020
Published by the National Vulnerability Database Dec 14, 2020
Reviewed May 21, 2021
Published to the GitHub Advisory Database Feb 11, 2022
Last updated Feb 16, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.105%
(44th percentile)

Weaknesses

CVE ID

CVE-2020-29509

GHSA ID

GHSA-xhqq-x44f-9fgg

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.