`CVE-2013-5679` OWASP Enterprise Security API

Affected software	OWASP Enterprise Security API
Severity	2.6 Low CVSS 2.0
Fixed in	`2.1.0`
Weakness	CWE-310
Published	30 Sep 2013
Updated	16 Jun 2026

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.

CWE-325

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 13 years ago.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS 2.4% chance in 30 days

Waratek protection

Protected by Waratek

Waratek has a rule that blocks attacks on this vulnerability.

Protection full
Action available patch rule
Review human ARMR file
Record active

Decided by	An ARMR patch file on disk for this CVE
Finding	CVE has an ARMR patch rule that provides mitigation

Decided by

An ARMR patch file on disk for this CVE

Finding

CVE has an ARMR patch rule that provides mitigation

ARMR rule files

1 file

The rule files Waratek ships for this CVE. Some CVEs need more than one, for example one per affected library or one per ARMR version.

CVE-2013-5679.armr patch rule, ARMR 2.6 added 2020-02-25 updated 2026-03-04

How to mitigate CVE-2013-5679

Upgrade OWASP Enterprise Security API to 2.1.0 or later. Until you can, Waratek RASP blocks exploitation with a rule written for this CVE. It runs inside the Java application, with no code changes.

Waratek RASP Runtime protection for Java applications

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.owasp.esapi:esapi 2.0.0 2.1.0 unbounded

Package	Introduced	Fixed	Last affected
`org.owasp.esapi:esapi`	2.0.0	`2.1.0`	unbounded

Products and versions

2 products, 3 version entries

Source	Vendor	Product	Scheme	Affected versions
osv	org.owasp.esapi	esapi	generic	≥ 2.0.0 and ＜ 2.1.0
nvd	owasp	enterprise security api	generic	2.0 · 2.0.1

Source

Vendor

Product

Scheme

Affected versions

osv

org.owasp.esapi

esapi

generic

≥ 2.0.0 and ＜ 2.1.0

nvd

owasp

enterprise security api

generic

2.0 · 2.0.1

References

URL	Tags
https://github.com/ESAPI/esapi-java-legacy/commit/41138fef5f63d9cf0d5e05d2bee2c7f682ffef3f	WEB
https://github.com/ESAPI/esapi-java-legacy	PACKAGE
http://code.google.com/p/owasp-esapi-java/issues/detail?id=306	WEB
http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.html	WEB
http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdf	WEB
http://www.securityfocus.com/bid/62415

URL

Timeline

Published	2013-09-30	By the CVE Program.
ARMR remediation created	2020-02-25	Earliest commit adding this CVE's ARMR patch or security rule.
ARMR remediation last updated	2026-03-04	Most recent commit touching this CVE's ARMR patch or security rule.
Last VRT activity	2026-03-04	Most recent commit touching this CVE's classification, patch or rule file.
NVD record modified	2026-06-16	NVD's own last-modified date for this record.

Published

2013-09-30

By the CVE Program.

ARMR remediation created

2020-02-25

Earliest commit adding this CVE's ARMR patch or security rule.

ARMR remediation last updated

2026-03-04

Most recent commit touching this CVE's ARMR patch or security rule.

Last VRT activity

2026-03-04

Most recent commit touching this CVE's classification, patch or rule file.

NVD record modified

2026-06-16

NVD's own last-modified date for this record.

How VRT decided (2 of 24 rules ran)

2 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file decided it matched Protected by Waratek ARMR patch file exists for this CVE

3 armr-secure-rule-file not reached An ARMR security-rule template on disk for this CVE

4 manual-classification not reached A researcher's recorded decision for this specific CVE

5 manual classification not reached Manual classification of this CVE in the legacy dataset

6 non-java-upstream not reached A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component not reached The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side not reached Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven not reached An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint not reached A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven not reached The affected package being open source on Maven, so the fix can be read

19 poc-derivable not reached An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit not reached Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match not reached A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc not reached Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold not reached Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published not reached Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

NVD ↗ · CVE.org ↗