CVE-2013-6440: OpenSAML-Java XML External Entity (XXE) Vulnerability

org.opensaml:opensaml Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Moderate
Not published

CVE-2013-6440: Exposure of Sensitive Information to an Unauthorized Actor in OpenSAML. Affects org.opensaml:opensaml versions < 2.6.1. Fixed in 2.6.1. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

OpenSAML is a Java library that provides a set of tools for implementing the Security Assertion Markup Language (SAML) standard. It is commonly used in identity and access management systems to enable secure single sign-on (SSO) authentication. The vulnerability affects versions of OpenSAML-Java prior to 2.6.1.

Vulnerability Detail

The vulnerability in OpenSAML-Java arises from the improper configuration of certain components, including the BasicParserPool, StaticBasicParserPool, XML Decrypter, and SAML Decrypter. These components set the expandEntityReferences property to true, which enables XML external entity (XXE) attacks. An attacker can exploit this vulnerability by crafting a malicious XML DOCTYPE declaration, leading to the exposure of sensitive information to unauthorized actors.

How To Fix

Minimum fixed version

2.6.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of OpenSAML-Java to mitigate the risk of XXE attacks.

Conclusion

The OpenSAML-Java XML External Entity (XXE) vulnerability exposes sensitive information to unauthorized actors. To mitigate this risk, it is crucial to update to OpenSAML-Java version 2.6.1 or later. For further assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.opensaml:opensaml →

Share this vulnerability

FAQ

OpenSAML-Java is a Java library used for implementing the SAML standard in identity and access management systems.

An XML external entity (XXE) attack is a type of vulnerability where an attacker can exploit the processing of XML entities to access sensitive information or execute arbitrary code.

This vulnerability allows remote attackers to conduct XXE attacks, potentially leading to the exposure of sensitive information stored in the affected OpenSAML-Java components.

No, only versions prior to 2.6.1 are affected. It is recommended to upgrade to the fixed version to mitigate the vulnerability.

No, the only effective solution is to update to OpenSAML-Java version 2.6.1 or later.

Related vulnerabilities

Recent vulnerabilities recorded for org.opensaml:opensaml.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

2.6.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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