CVE-2013-5960: Missing Cryptographic Step in OWASP Enterprise Security API for Java

CVE-2013-5960 · Severity: info · Published 2022-05-14

Missing Cryptographic Step in OWASP Enterprise Security API for Java

Technologies: org.owasp.esapi:esapi (Maven). Vendors: Maven.

Quick answers

Is CVE-2013-5960 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-5960 being exploited in the wild.
How severe is CVE-2013-5960?
Informational severity, published 14 May 2022.
Which products and versions are affected?
org.owasp.esapi:esapi (Maven) ECOSYSTEM:introduced=2.0.0.0,fixed=2.1.0.1.
Is there a fix for CVE-2013-5960?
Yes. org.owasp.esapi:esapi (Maven): upgrade to 2.1.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-5960?
Check whether you run org.owasp.esapi:esapi (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.owasp.esapi:esapi (Maven): upgrade to 2.1.0.1 or later
    # set org.owasp.esapi:esapi to 2.1.0.1 in your pom.xml or build.gradle

Affected products

  • org.owasp.esapi:esapi (Maven) ECOSYSTEM:introduced=2.0.0.0,fixed=2.1.0.1

Identifiers

  • CVE-2013-5960
  • GHSA-2g56-7jv7-wxxq

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.