CVE-2013-5679 Missing Cryptographic Step in OWASP Enterprise Security API for Java

Low 2.6 Published Updated

Remote attackers can bypass cryptographic protections in the OWASP ESAPI Java library by tampering with serialized ciphertext due to improper MAC handling.

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-5679?

CVE-2013-5679 is a low-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 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 authenticity in the default configuration, involving a null MAC and a zero MAC length.

Weakness: CWE-310

Which versions are affected by CVE-2013-5679?

2 open source packages ship an affected version, including org.owasp.esapi:esapi. It affects 1 product.

PackageAffectedFixed in
org.owasp.esapi:esapi MavenFrom 2.0.02.1.0
org.owasp.esapi:esapi MavenFrom 2.0.02.1.0

Products include Owasp Enterprise Security Api.

How do I fix CVE-2013-5679?

Upgrade org.owasp.esapi:esapi to 2.1.0 or later.

Is CVE-2013-5679 being exploited?

There is no known exploitation of CVE-2013-5679 in the wild and no public exploit code.

Sources

Also known as GHSA-jcp9-796g-pv9p, MGASA-2015-0064.

Is CVE-2013-5679 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free