How severe is GHSA-5684-g483-2249?

No CVSS score has been assigned to GHSA-5684-g483-2249 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5684-g483-2249?

GHSA-5684-g483-2249 affects the following packages: github.com/russellhaering/gosaml2 (Go). Ecosystems affected: Go.

How do I fix GHSA-5684-g483-2249?

Update github.com/russellhaering/gosaml2 to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5684-g483-2249 is resolved across your whole dependency graph.

How do I detect GHSA-5684-g483-2249 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/russellhaering/gosaml2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5684-g483-2249 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-5684-g483-2249 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5684-g483-2249 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5684-g483-2249 published, and has it been updated?

GHSA-5684-g483-2249 was published on May 24, 2021 and was last updated on October 5, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Signature Validation BypassGHSA-5684-g483-2249

GHSA-5684-g483-2249 is a security vulnerability in github.com/russellhaering/gosaml2. A fix is available for github.com/russellhaering/gosaml2 — see the affected versions and patch details below.

Published

May 24, 2021

Updated

Oct 5, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 5, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/russellhaering/gosaml2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/russellhaering/gosaml2`	all versions	0.5.0`go get github.com/russellhaering/gosaml2@v0.5.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/russellhaering/gosaml2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/russellhaering/gosaml2 to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5684-g483-2249 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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](https://github.com/russellhaeri

O3 Security · Impact-Aware SCA

Is GHSA-5684-g483-2249 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works