# Missing Cryptographic Step in OWASP Enterprise Security API for Java

Advisory record · `GHSA-jcp9-796g-pv9p`

- **Identifiers:** `GHSA-jcp9-796g-pv9p` · `CVE-2013-5679`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-325](https://cwe.mitre.org/data/definitions/325.html)
- **Tags:** [CWE-325](https://agentprime.io/advisories/tag/cwe-325.md)
- **Published:** 17 May 2022
- **Updated:** 28 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.owasp.esapi:esapi` (Maven): affected `>=2.0.0, <2.1.0`; fixed in `2.1.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.024, the 84th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jcp9-796g-pv9p)

## Sources

- [GitHub Advisory Database: GHSA-jcp9-796g-pv9p](https://github.com/advisories/GHSA-jcp9-796g-pv9p)
- [OSV: GHSA-jcp9-796g-pv9p](https://osv.dev/vulnerability/GHSA-jcp9-796g-pv9p)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-5679>
- <https://github.com/ESAPI/esapi-java-legacy/commit/41138fef5f63d9cf0d5e05d2bee2c7f682ffef3f>
- <https://github.com/ESAPI/esapi-java-legacy>
- <http://code.google.com/p/owasp-esapi-java/issues/detail?id=306>
- <http://lists.owasp.org/pipermail/esapi-dev/2013-August/002285.html>
- <http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/ESAPI-security-bulletin1.pdf>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jcp9-796g-pv9p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jcp9-796g-pv9p/>. Everything for agents: <https://agentprime.io/llms.txt>.