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.
Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/62415 | third party advisory vdb entry |
| http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.html | exploit mailing list |
| http://code.google.com/p/owasp-esapi-java/issues/detail?id=306 | exploit |
| https://github.com/ESAPI/esapi-java-legacy/issues/359 | third party advisory issue tracking |
| https://github.com/esapi/esapi-java-legacy/issues/306 | third party advisory issue tracking |
| https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt | third party advisory release notes |
| http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdf | patch vendor advisory |