Summary
crewjam/saml vulnerable to signature bypass via multiple Assertion elements due to improper authentication
Credit
This issue was reported by Felix Wilhelm from Google Project Zero.
Impact
The crewjam/saml go library is vulnerable to an authentication bypass when processing SAML responses containing multiple Assertion elements.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2022-41912 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.9); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This issue has been corrected in version 0.4.9.
Frequently Asked Questions
- What is CVE-2022-41912? CVE-2022-41912 is a critical-severity improper authentication vulnerability in github.com/crewjam/saml (go), affecting versions < 0.4.9. It is fixed in 0.4.9. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2022-41912? CVE-2022-41912 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/crewjam/saml are affected by CVE-2022-41912? github.com/crewjam/saml (go) versions < 0.4.9 is affected.
- Is there a fix for CVE-2022-41912? Yes. CVE-2022-41912 is fixed in 0.4.9. Upgrade to this version or later.
- Is CVE-2022-41912 exploitable, and should I be worried? Whether CVE-2022-41912 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-41912 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-41912? Upgrade
github.com/crewjam/samlto 0.4.9 or later.