CVE-2013-5960
Apache ESAPI Java Tampering Vulnerability
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.
INFO
Published Date :
Sept. 30, 2013, 5:09 p.m.
Last Modified :
Nov. 21, 2024, 1:58 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
4.9
Exploitability Score :
8.6
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2013-5960.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2013-5960 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2013-5960 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Modified Analysis by [email protected]
Feb. 04, 2019
Action Type Old Value New Value Changed Reference Type http://www.securityfocus.com/bid/62415 No Types Assigned http://www.securityfocus.com/bid/62415 Third Party Advisory, VDB Entry Changed Reference Type https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt No Types Assigned https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt Release Notes, Third Party Advisory Changed Reference Type https://github.com/esapi/esapi-java-legacy/issues/306 No Types Assigned https://github.com/esapi/esapi-java-legacy/issues/306 Issue Tracking, Third Party Advisory Changed Reference Type https://github.com/ESAPI/esapi-java-legacy/issues/359 No Types Assigned https://github.com/ESAPI/esapi-java-legacy/issues/359 Issue Tracking, Third Party Advisory Changed CPE Configuration OR *cpe:2.3:a:owasp:enterprise_security_api:2.0:*:*:*:*:*:*:* *cpe:2.3:a:owasp:enterprise_security_api:2.0.1:*:*:*:*:*:*:* *cpe:2.3:a:owasp:enterprise_security_api:2.1.0:*:*:*:*:*:*:* OR *cpe:2.3:a:owasp:enterprise_security_api:*:*:*:*:*:*:*:* versions from (including) 2.0 up to (excluding) 2.1.0.1 -
CVE Modified by [email protected]
Nov. 23, 2017
Action Type Old Value New Value Changed Description The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.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. 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. Added Reference https://github.com/ESAPI/esapi-java-legacy/issues/359 [No Types Assigned] Added Reference https://github.com/esapi/esapi-java-legacy/issues/306 [No Types Assigned] Added Reference https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txt [No Types Assigned] -
Modified Analysis by [email protected]
May. 06, 2016
Action Type Old Value New Value Changed CPE Configuration Configuration 1 OR *cpe:2.3:a:owasp:enterprise_security_api:2.0.1:*:*:*:*:*:*:* Configuration 1 OR *cpe:2.3:a:owasp:enterprise_security_api:2.1.0:*:*:*:*:*:*:* *cpe:2.3:a:owasp:enterprise_security_api:2.0:*:*:*:*:*:*:* *cpe:2.3:a:owasp:enterprise_security_api:2.0.1:*:*:*:*:*:*:* -
Initial Analysis by [email protected]
Oct. 01, 2013
Action Type Old Value New Value
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2013-5960 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2013-5960
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.53 }} 0.08%
score
0.77186
percentile