Enterprise Security Api
Approved changes feed: RSS · Atom
cpe:2.3:a:owasp:enterprise_security_api:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Owasp (b778b703-6f88-5eeb-b966-330b456a6d00) |
|---|---|
| Product | Enterprise Security Api (9d080ec6-6a7a-5631-ba28-88a03758cc48) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/esapi/esapi-java-legacy |
purl2cpe | 2026-06-01 10:12:06.958580 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-24891 |
vulnerable | 2026-06-03 14:46:36.538953 |
Cross-site Scripting in org.owasp.esapi:esapi -- antisamy-esapi.xml configuration file
MEDIUM (5.4)
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, there is a potential for a cross-site scripting vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the **antisamy-esapi.xml** configuration file that can cause "javascript:" URLs to fail to be correctly sanitized. This issue is patched in ESAPI 2.3.0.0. As a workaround, manually edit the **antisamy-esapi.xml** configuration files to change the "onsiteURL" regular expression. More information about remediation of the vulnerability, including the workaround, is available in the maintainers' release notes and security bulletin.
Published: 2022-04-27T00:00:00.000Z
Updated: 2025-11-03T19:26:55.130Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23457 |
vulnerable | 2026-06-03 14:46:27.471523 |
Path Traversal in ESAPI
HIGH (7.5)
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.
Published: 2022-04-25T00:00:00.000Z
Updated: 2025-11-03T19:26:49.494Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2013-5960 |
vulnerable | 2026-06-03 14:33:24.440695 |
Details available
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, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679.
Published: 2013-09-30T10:00:00.000Z
Updated: 2024-08-06T17:29:42.682Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.