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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/62415 | Third Party Advisory VDB Entry |
http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdf | Patch Vendor Advisory |
http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.html | Exploit |
http://code.google.com/p/owasp-esapi-java/issues/detail?id=306 | Exploit |
https://github.com/ESAPI/esapi-java-legacy/issues/359 | Issue Tracking Third Party Advisory |
https://github.com/esapi/esapi-java-legacy/issues/306 | Issue Tracking Third Party Advisory |
https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt | Release Notes Third Party Advisory |
Configurations
Information
Published : 2013-09-30 10:09
Updated : 2019-02-04 08:33
NVD link : CVE-2013-5960
Mitre link : CVE-2013-5960
JSON object : View
CWE
CWE-310
Cryptographic Issues
Products Affected
owasp
- enterprise_security_api