Summary
Improper Authentication in OpenSAML
Shibboleth OpenSAML library 2.4.x before 2.4.3 and 2.5.x before 2.5.1, and IdP before 2.3.2, allows remote attackers to forge messages and bypass authentication via an "XML Signature wrapping attack."
Impact
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.
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
org.opensaml:opensaml to 2.4.3 or later; org.opensaml:opensaml to 2.5.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2011-1411? CVE-2011-1411 is a medium-severity improper authentication vulnerability in org.opensaml:opensaml (maven), affecting versions >= 2.4.0, < 2.4.3. It is fixed in 2.4.3, 2.5.1. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of org.opensaml:opensaml are affected by CVE-2011-1411? org.opensaml:opensaml (maven) versions >= 2.4.0, < 2.4.3 is affected.
- Is there a fix for CVE-2011-1411? Yes. CVE-2011-1411 is fixed in 2.4.3, 2.5.1. Upgrade to this version or later.
- Is CVE-2011-1411 exploitable, and should I be worried? Whether CVE-2011-1411 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-2011-1411 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-2011-1411?
- Upgrade
org.opensaml:opensamlto 2.4.3 or later - Upgrade
org.opensaml:opensamlto 2.5.1 or later
- Upgrade