First published: Mon Sep 30 2013(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
OWASP Enterprise Security API | =2.0 | |
OWASP Enterprise Security API | =2.0.1 | |
maven/org.owasp.esapi:esapi | >=2.0.0<2.1.0 | 2.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-5679 has a Medium severity due to its potential to allow remote attackers to tamper with encrypted ciphertext.
To fix CVE-2013-5679, upgrade to OWASP Enterprise Security API version 2.1.0 or later.
CVE-2013-5679 may allow an attacker to bypass cryptographic protections, leading to unauthorized data access or manipulation.
CVE-2013-5679 affects OWASP ESAPI versions 2.0 and 2.0.1.
Yes, CVE-2013-5679 can be exploited remotely by attackers to manipulate encrypted data.