CVE-2013-5960 Missing Cryptographic Step in OWASP Enterprise Security API for Java
Remote attackers can bypass cryptographic protections in OWASP ESAPI Java by tampering with serialized ciphertext in non-default configurations.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2013-5960?
CVE-2013-5960 is a medium-severity vulnerability in n/a, published on 30 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-310
Which versions are affected by CVE-2013-5960?
2 open source packages ship an affected version, including org.owasp.esapi:esapi. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.owasp.esapi:esapi Maven | From 2.0.0.0 | 2.1.0.1 |
org.owasp.esapi:esapi Maven | From 2.0.0.0 | 2.1.0.1 |
Products include Owasp Enterprise Security Api.
How do I fix CVE-2013-5960?
Upgrade org.owasp.esapi:esapi to 2.1.0.1 or later.
Is CVE-2013-5960 being exploited?
There is no known exploitation of CVE-2013-5960 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-2g56-7jv7-wxxq.