How severe is GHSA-rrfw-hg9m-j47h?

No CVSS score has been assigned to GHSA-rrfw-hg9m-j47h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rrfw-hg9m-j47h?

GHSA-rrfw-hg9m-j47h affects the following packages: github.com/russellhaering/goxmldsig (Go). Ecosystems affected: Go.

How do I fix GHSA-rrfw-hg9m-j47h?

Update github.com/russellhaering/goxmldsig to 0.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrfw-hg9m-j47h is resolved across your whole dependency graph.

How do I detect GHSA-rrfw-hg9m-j47h in my Go dependencies?

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

How do I mitigate GHSA-rrfw-hg9m-j47h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rrfw-hg9m-j47h?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rrfw-hg9m-j47h can be triaged on real exposure rather than presence alone.

Is GHSA-rrfw-hg9m-j47h actively exploited in the wild?

No public exploit code has been indexed for GHSA-rrfw-hg9m-j47h 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-rrfw-hg9m-j47h published, and has it been updated?

GHSA-rrfw-hg9m-j47h was published on May 24, 2021 and was last updated on October 8, 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

GHSA-rrfw-hg9m-j47h — goxmldsig

GHSA-rrfw-hg9m-j47h is a security vulnerability in github.com/russellhaering/goxmldsig. A fix is available for github.com/russellhaering/goxmldsig — see the affected versions and patch details below.

Signature Validation Bypass

Published

May 24, 2021

Updated

Oct 8, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐹github.com/russellhaering/goxmldsig

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

An authentication bypass exists in the goxmldsig this library uses to determine if SAML assertions are genuine. An attacker could craft a SAML response that would appear to be valid but would not have been genuinely issued by the IDP.

Patches

Version 0.4.2 bumps the dependency which should fix the issue.

For more information

Please see the advisory in goxmldsig

Credits

The original vulnerability was discovered by @jupenur. Thanks to @russellhaering for the heads up.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/russellhaering/goxmldsig`	all versions	0.4.2`go get github.com/russellhaering/goxmldsig@v0.4.2`

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/goxmldsig, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/russellhaering/goxmldsig to 0.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrfw-hg9m-j47h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rrfw-hg9m-j47h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rrfw-hg9m-j47h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An authentication bypass exists in the [goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) this library uses to determine if SAML assertions are genuine. An attacker could craft a SAML response that would appear to be valid but would not have been genuinely issued by the IDP. ### Patches Version 0.4.2 bumps the dependency which should fix the issue. ### For more information Please see [the advisory in goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) ## Credits The original vulnerabilit

O3 Security · Impact-Aware SCA

Is GHSA-rrfw-hg9m-j47h in your dependencies?

O3 Security finds GHSA-rrfw-hg9m-j47h across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works