Enterprise Security API vulnerabilitiesRanked by how likely they are to be used.
Enterprise Security API is made by Owasp. We track 4 published vulnerabilities listed under that exact name, across 11 versions. None of them is on the list of flaws known to be exploited today. Owasp lists newer releases under their own names, such as Enterprise Security API for Java, so check those pages too.
We keep watching the known-exploited list.
Is Enterprise Security API listed under other names? Yes.
Owasp also lists Enterprise Security API under more specific names, such as Enterprise Security API for Java. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Enterprise Security API vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Enterprise Security API's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Enterprise Security API flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.8%CVE-2022-23457High
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library.
- 2.4%
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,...
- 1.7%CVE-2022-24891Medium
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library.
- 1.7%CVE-2013-5960Medium
The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext,...
Running Enterprise Security API? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one's own implementation of the Validator interface. However, maintainers do not recommend this.
- Matched to
- Enterprise Security API on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Enterprise Security API, across 11 versions.
None of Enterprise Security API's vulnerabilities is on the list of flaws known to be exploited today.
Owasp also lists Enterprise Security API under more specific names, such as Enterprise Security API for Java. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Enterprise Security API. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.