CVE-2013-5960

Name: CVE-2013-5960
Creator: NVD / NIST
Published: 2013-09-30T17:09:26.067+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.65%

Last modified Jun 16, 2026

CVE-2013-5960 is a vulnerability of currently unknown severity. The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679.. EPSS estimates a 1.65% chance of exploitation in the next 30 days.

Description

The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679.

Metrics

EPSS Probability

1.65%

73.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-310

Affected Software

Vendor	Product	Versions
Owasp	Enterprise Security Api	>= 2.0, < 2.1.0.1

References

http://code.google.com/p/owasp-esapi-java/issues/detail?id=306Exploit
http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.htmlExploit
http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdfPatch, Vendor Advisory
http://www.securityfocus.com/bid/62415Third Party Advisory, VDB Entry
https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txtRelease Notes, Third Party Advisory
https://github.com/ESAPI/esapi-java-legacy/issues/359Issue Tracking, Third Party Advisory
https://github.com/esapi/esapi-java-legacy/issues/306Issue Tracking, Third Party Advisory
http://code.google.com/p/owasp-esapi-java/issues/detail?id=306Exploit
http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.htmlExploit
http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdfPatch, Vendor Advisory
http://www.securityfocus.com/bid/62415Third Party Advisory, VDB Entry
https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txtRelease Notes, Third Party Advisory
https://github.com/ESAPI/esapi-java-legacy/issues/359Issue Tracking, Third Party Advisory
https://github.com/esapi/esapi-java-legacy/issues/306Issue Tracking, Third Party Advisory

Timeline

Published: Sep 30, 2013
Last Modified: Jun 16, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2013-5960?

How severe is CVE-2013-5960?

Severity scoring for CVE-2013-5960 is pending analysis. The EPSS model estimates a 1.65% probability of exploitation in the next 30 days.

How do I fix CVE-2013-5960?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-5960?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST