CVE-2013-5960: Missing Cryptographic Step in OWASP Enterprise Security API for Java
Summary
CVE-2013-5960: Missing Cryptographic Step in OWASP Enterprise Security API for Java. Affects org.owasp.esapi:esapi versions >= 2.0.0.0, < 2.1.0.1. Fixed in 2.1.0.1. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The OWASP Enterprise Security API (ESAPI) for Java is a library that provides a set of security functions for Java applications. It aims to simplify the implementation of security controls and protect against common security vulnerabilities. The ESAPI library includes features for symmetric encryption, including authenticated-encryption. However, a vulnerability has been discovered in the symmetric-encryption implementation of ESAPI for Java versions 2.x before 2.1.0.1.
Vulnerability Detail
The vulnerability in the authenticated-encryption feature of ESAPI for Java allows remote attackers to bypass cryptographic protection mechanisms by tampering with serialized ciphertext. This can be exploited by attacking the intended cipher mode in a non-default configuration. The vulnerability is different from CVE-2013-5679. The impact of this vulnerability is that it weakens the cryptographic protection provided by ESAPI, potentially allowing unauthorized access to sensitive data.
How To Fix
Latest published version: 2.7.0.1-RC1 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.1.0.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 specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed version of the OWASP ESAPI library.
Conclusion
The missing cryptographic step vulnerability in the OWASP ESAPI library for Java versions 2.x before 2.1.0.1 can weaken the cryptographic protection of applications using this library. It is recommended to upgrade to the fixed version of the library to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for org.owasp.esapi:esapi →
FAQ
OWASP ESAPI for Java is a library that provides security functions for Java applications, helping developers implement security controls and protect against common vulnerabilities.
The vulnerability allows remote attackers to bypass cryptographic protection mechanisms and potentially gain unauthorized access to sensitive data.
There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed version of the OWASP ESAPI library.
This vulnerability is different from CVE-2013-5679. While both vulnerabilities affect the OWASP ESAPI library for Java, they have different origins and technical aspects.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software using just the pom.xml file.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.owasp.esapi:esapi.
