{"answers":{"affected":"2 open source packages ship an affected version, including org.owasp.esapi:esapi. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-5960 in the wild and no public exploit code.","fix":"Upgrade org.owasp.esapi:esapi to 2.1.0.1 or later.","what":"CVE-2013-5960 is a medium-severity vulnerability in n/a, published on 30 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5960 and fix it if it is affected.\n\nWhat it is: CVE-2013-5960 is a medium-severity vulnerability in n/a, published on 30 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-5960 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.owasp.esapi:esapi (Maven): affected from 2.0.0.0; fixed in 2.1.0.1\n- org.owasp.esapi:esapi (Maven): affected from 2.0.0.0; fixed in 2.1.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2013-5960/ (Markdown: https://insights.sbomify.com/CVE-2013-5960/index.md)","id":"CVE-2013-5960","markdown":"https://insights.sbomify.com/CVE-2013-5960/index.md","name":"CVE-2013-5960","record":{"aliases":["GHSA-2g56-7jv7-wxxq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Java security library","requires_auth":"none","summary":"Remote attackers can bypass cryptographic protections in OWASP ESAPI Java by tampering with serialized ciphertext in non-default configurations.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise_security_api","vendor":"owasp"}],"cvss":{"score":5.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Missing Cryptographic Step in OWASP Enterprise Security API for Java","id":"CVE-2013-5960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2013"},"n_packages":2,"n_references":7,"next":{"headline":"File upload in n/a","id":"CVE-2013-5961"},"packages":[{"ecosystem":"Maven","fixed":["2.1.0.1"],"introduced":["2.0.0.0"],"last_affected":[],"package":"org.owasp.esapi:esapi","purl":null,"source":"GHSA-2g56-7jv7-wxxq"},{"ecosystem":"Maven","fixed":["2.1.0.1"],"introduced":["2.0.0.0"],"last_affected":[],"package":"org.owasp.esapi:esapi","purl":"pkg:maven/org.owasp.esapi/esapi","source":"GHSA-2g56-7jv7-wxxq"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2013-5959"},"products":["n/a"],"published":"2013-09-30","related":[{"cvss_score":2.6,"headline":"Missing Cryptographic Step in OWASP Enterprise Security API for Java","id":"CVE-2013-5679","kev_date_added":null,"published":"2013-09-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can bypass cryptographic protections in OWASP ESAPI Java by tampering with serialized ciphertext in non-default configurations.","url":"https://insights.sbomify.com/CVE-2013-5960/"}