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.
Remediation
References
http://www.securityfocus.com/bid/62415
http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdf
http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.html
http://code.google.com/p/owasp-esapi-java/issues/detail?id=306
https://github.com/ESAPI/esapi-java-legacy/issues/359
https://github.com/esapi/esapi-java-legacy/issues/306
https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt
Related Vulnerabilities
CVE-2016-10529 Vulnerability in npm package droppy
CVE-2016-10556 Vulnerability in npm package sequelize
CVE-2017-9791 Vulnerability in maven package org.apache.struts:struts2-struts1-plugin
CVE-2022-37259 Vulnerability in npm package steal
CVE-2018-3737 Vulnerability in maven package org.webjars.npm:sshpk