CVE-2011-1411: Improper Authentication in OpenSAML

org.opensaml:opensaml Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Moderate
Not published

CVE-2011-1411: Improper Authentication in OpenSAML. Affects org.opensaml:opensaml across 2 version ranges.

>= 2.4.0, < 2.4.3 >= 2.5.0, < 2.5.1

Fixed in 2.4.3 or 2.5.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

OpenSAML is a library used for implementing the Security Assertion Markup Language (SAML) protocol. It provides functionality for creating, manipulating, and validating SAML messages. The vulnerability affects versions 2.4.x before 2.4.3 and 2.5.x before 2.5.1 of the Shibboleth OpenSAML library, as well as versions before 2.3.2 of the Identity Provider (IdP).

Vulnerability Detail

The vulnerability in OpenSAML allows remote attackers to forge messages and bypass authentication through an XML Signature wrapping attack. This attack involves manipulating the XML Signature element in a SAML message to wrap it around other elements, tricking the recipient into accepting the forged message as authentic. This can lead to unauthorized access and potential security breaches.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.4.0, < 2.4.3 2.4.3
  • >= 2.5.0, < 2.5.1 2.5.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the fixed versions of the affected packages.

Conclusion

The vulnerability in OpenSAML allows for the forging of messages and bypassing of authentication through an XML Signature wrapping attack. To mitigate this vulnerability, it is crucial to upgrade to the fixed versions of the affected packages. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.opensaml:opensaml →

Share this vulnerability

FAQ

OpenSAML is a library used for implementing the Security Assertion Markup Language (SAML) protocol. It provides functionality for creating, manipulating, and validating SAML messages.

An XML Signature wrapping attack is a technique used to manipulate the XML Signature element in a SAML message to wrap it around other elements, tricking the recipient into accepting the forged message as authentic.

The vulnerability allows remote attackers to bypass authentication and forge messages, potentially leading to unauthorized access and security breaches.

To fix the vulnerability, it is recommended to upgrade to the fixed versions of the affected packages. For Shibboleth OpenSAML library, upgrade to version 2.4.3 or later for 2.4.x series, and version 2.5.1 or later for 2.5.x series. For the Identity Provider (IdP), upgrade to version 2.3.2 or later.

There is no known workaround for this vulnerability. It is important to apply the recommended fix by upgrading to the fixed versions of the affected packages.

Related vulnerabilities

Recent vulnerabilities recorded for org.opensaml:opensaml.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.4.0, < 2.4.3 2.4.3
  • >= 2.5.0, < 2.5.1 2.5.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback