CVE-2013-5960

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.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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
1.655%
chance of exploitation in the next 30 days
higher than 77% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 2
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2013-09-30Published by the CNA10:00 UTC
  2. 2022-05-14GitHub advisory published (GHSA-2g56-7jv7-wxxq)3148 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-2g56-7jv7-wxxq, affected packages:

PackageVulnerable versionsFixed in
Maven org.owasp.esapi:esapifrom 2.0.0.0 before 2.1.0.12.1.0.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
owasp enterprise_security_apifrom 2.0 before 2.1.0.1fixed in 2.1.0.12.1.0.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources