CVE-2022-41912 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in github.com/crewjam/saml. A fix is available for github.com/crewjam/saml — see the affected versions and patch details below.
crewjam/saml go library is vulnerable to signature bypass via multiple Assertion elements
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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 CVE-2022-41912.
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/crewjam/samlReal-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
The crewjam/saml go library is vulnerable to an authentication bypass when processing SAML responses containing multiple Assertion elements.
Patches
This issue has been corrected in version 0.4.9.
Credit
This issue was reported by Felix Wilhelm from Google Project Zero.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/crewjam/saml | all versions | 0.4.9go get github.com/crewjam/saml@v0.4.9 |
Affected Products
samlsaml_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crewjam/saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/crewjam/saml to 0.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41912 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.
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.
Whilst the Red Hat Advanced Cluster Management for Kubernetes (RHACM) acm-grafana container include the vulnerable underscore library, the access to it is protected by OpenShift OAuth. Therefore the impact by this flaw is reduced from Critical to Important. The OCP grafana-container includes the vulnerable underscore…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ceph Storage 6.1 | rhceph/rhceph-6-dashboard-rhel9:6-75 | RHSA-2023:3642 |
| Red Hat OpenShift Container Platform 4.10 | openshift4/ose-grafana:v4.10.0-202301040925.p0.gca476d4.assembly.stream | RHSA-2023:0032 |
| Red Hat OpenShift Container Platform 4.11 | openshift4/ose-grafana:v4.11.0-202212190555.p0.gbc05ec1.assembly.stream | RHSA-2022:9108 |
| Red Hat OpenShift Container Platform 4.8 | openshift4/ose-grafana:v4.8.0-202301100925.p0.g7156d02.assembly.stream | RHSA-2023:0237 |
| Red Hat OpenShift Container Platform 4.9 | openshift4/ose-grafana:v4.9.0-202301301454.p0.g06135eb.assembly.stream | RHSA-2023:0574 |
Frequently Asked Questions
Is CVE-2022-41912 in your dependencies?
Find it across Go, including transitive dependencies.