Skip to content
Fencer Intel
low 2.6

CVE-2013-5679 json

Missing Cryptographic Step in OWASP Enterprise Security API for Java

published 2013-09-30 13 y ago modified 2026-06-16 4 mo ago also GHSA-jcp9-796g-pv9p , EUVD-2022-4332

cvss
2.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.owasp.esapi:esapi 2.1.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-5679 updated cvss 5.6

owasp-esapi-java: symmetric encryption MAC bypass

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.43% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • code.google.com http://code.google.com/p/owasp-esapi-java/issues/detail?id=306 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.6 AV:L/AC:H/Au:N/C:P/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.owasp.esapi:esapi
>=2.0.0, <2.1.0
2.1.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.