CVE-2013-5960
Last modified
CVE-2013-5960 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.65% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Owasp | Enterprise Security Api | >= 2.0, < 2.1.0.1 |
References
- http://www.securityfocus.com/bid/62415Third Party Advisory, VDB Entry
- https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txtRelease Notes, Third Party Advisory
- https://github.com/ESAPI/esapi-java-legacy/issues/359Issue Tracking, Third Party Advisory
- https://github.com/esapi/esapi-java-legacy/issues/306Issue Tracking, Third Party Advisory
- http://www.securityfocus.com/bid/62415Third Party Advisory, VDB Entry
- https://github.com/ESAPI/esapi-java-legacy/blob/master/documentation/esapi4java-core-2.1.0.1-release-notes.txtRelease Notes, Third Party Advisory
- https://github.com/ESAPI/esapi-java-legacy/issues/359Issue Tracking, Third Party Advisory
- https://github.com/esapi/esapi-java-legacy/issues/306Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-5960?
How severe is CVE-2013-5960?
How do I fix CVE-2013-5960?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-5954Multiple cross-site request forgery (CSRF) vulnerabilities i…
- CVE-2013-5955Cross-site scripting (XSS) vulnerability in manage.php in th…
- CVE-2013-5956Cross-site scripting (XSS) vulnerability in includes/flvthum…
- CVE-2013-5957Multiple SQL injection vulnerabilities in CRM/Core/Page/AJAX…
- CVE-2013-5958The Security component in Symfony 2.0.x before 2.0.25, 2.1.x…
- CVE-2013-5959Blue Coat ProxySG before 6.2.14.1, 6.3.x, 6.4.x, and 6.5 bef…
- CVE-2013-5961Unrestricted file upload vulnerability in lazyseo.php in the…
- CVE-2013-5962Unrestricted file upload vulnerability in frames/upload-imag…
- CVE-2013-5963Unrestricted file upload vulnerability in multi.php in Simpl…
- CVE-2013-5964Cross-site scripting (XSS) vulnerability in the administrati…
- CVE-2013-5965The Node View Permissions module 7.x-1.x before 7.x-1.2 for …
- CVE-2013-5966Cross-site scripting (XSS) vulnerability in ZK Framework bef…
Are you affected by CVE-2013-5960?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
