gosaml2 vulnerable to Denial Of Service Via Deflate Decompression BombGHSA-6gc3-crp7-25w5
MEDIUMFix: russellhaering/gosaml2@f9d6604GHSA-6gc3-crp7-25w5 is a medium-severity (CVSS 5.3) CWE-409 vulnerability in github.com/russellhaering/gosaml2. A fix is available for github.com/russellhaering/gosaml2 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6gc3-crp7-25w5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/russellhaering/gosaml2Real-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
gosaml2 is a Pure Go implementation of SAML 2.0. SAML Service Providers using this library for SAML authentication support are likely susceptible to Denial of Service attacks. A bug in this library enables attackers to craft a deflate-compressed request which will consume significantly more memory during processing than the size of the original request. This may eventually lead to memory exhaustion and the process being killed. The maximum compression ratio achievable with deflate is 1032:1, so by limiting the size of bodies passed to gosaml2, limiting the rate and concurrency of calls, and ensuring that lots of memory is available to the process it may be possible to help Go's garbage collector "keep up". Implementors are encouraged not to rely on this. This issue is fixed in version 0.9.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/russellhaering/gosaml2 | all versions | 0.9.0go get github.com/russellhaering/gosaml2@v0.9.0 |
Affected Products
gosaml2gosaml2_projectDetection & mitigation playbook
Open-source dependencyDetect
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.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gc3-crp7-25w5 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The maximum compression ratio achievable with deflate is 1032:1. By limiting the size of bodies passed to gosaml2, limiting the rate and concurrency of calls, and ensuring that lots of memory is available to the process, it may be possible to help Go's garbage collector "keep up".Source: Red Hat security advisory for GHSA-6gc3-crp7-25w5 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-6gc3-crp7-25w5 in your dependencies?
Find it across Go, including transitive dependencies.