How severe is CVE-2010-3300?

CVE-2010-3300 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2010-3300 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2010-3300?

CVE-2010-3300 primarily affects Owasp Enterprise Security Api For Java. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2010-3300?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2010-3300 published?

CVE-2010-3300 was published on 2021-06-22 and last updated on 2026-06-16.

CVE-2010-3300

CVE-2010-3300 is a medium-severity vulnerability in Owasp Enterprise Security Api For Java with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-649.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 4.3
EPSS exploit prediction: 0% (36th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-649
Affected product: Owasp Enterprise Security Api For Java
Published: 2021-06-22
Last modified: 2026-06-16

Description

It was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.

Frequently asked questions

What is CVE-2010-3300?: It was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.
How severe is CVE-2010-3300?: CVE-2010-3300 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2010-3300 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-3300?: CVE-2010-3300 primarily affects Owasp Enterprise Security Api For Java. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-3300?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-3300 published?: CVE-2010-3300 was published on 2021-06-22 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:owasp:enterprise_security_api_for_java:*:*:*:*:*:*:*:*
cpe:2.3:a:owasp:enterprise_security_api_for_java:2.0:-:*:*:*:*:*:*
cpe:2.3:a:owasp:enterprise_security_api_for_java:2.0:rc1:*:*:*:*:*:*

Other CWE-649 vulnerabilities

CVE-2024-10772 — High (CVSS 8.8): Since the firmware update is not validated, an attacker can install modified firmware on the device. This has a high…
CVE-2025-41351 — Medium (CVSS 6.0): Vulnerability that allows a Padding Oracle Attack to be performed on the Funambol v30.0.0.20 cloud server. The…
CVE-2024-36279 — Medium (CVSS 5.3): Reliance on obfuscation or encryption of security-relevant inputs without integrity checking issue exists in "FreeFrom…

Browse all CWE-649 vulnerabilities →