LiveActive security incident?Get immediate response
CVE Record

CVE-2013-5960: The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Sec...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-5960 affects OWASP ESAPI for Java 2.x before 2.1.0.1. In a non-default authenticated-encryption configuration, tampered serialized ciphertext may not be properly rejected, weakening cryptographic protections that applications expect to enforce. Exposure is most likely in Java applications using OWASP ESAPI 2.x before 2.1.0.1 with the affected non-default authenticated-encryption configuration and serialized ciphertext processing. Treat this as a targeted legacy-library risk. Prioritize validation if ESAPI Java protects authentication, authorization, session state, or sensitive workflow data. Urgency is lower without evidence of active exploitation, but cryptographic bypass risk warrants cleanup. Mitigation focus: Inventory applications using OWASP ESAPI for Java 2.x.; Upgrade ESAPI Java to 2.1.0.1 or later where applicable.; Review OWASP ESAPI release notes and security bulletin before deployment..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-5960 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.