{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2013-0425 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2013-0425 is a critical vulnerability in Oracle Jdk, published on 2 Feb 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-0425 and fix it if it is affected.\n\nWhat it is: CVE-2013-0425 is a critical vulnerability in Oracle Jdk, published on 2 Feb 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-0425 in the wild and no public exploit code.\n\nAffected product: Oracle Jdk. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-0425/ (Markdown: https://insights.sbomify.com/CVE-2013-0425/index.md)","id":"CVE-2013-0425","markdown":"https://insights.sbomify.com/CVE-2013-0425/index.md","name":"CVE-2013-0425","record":{"aliases":["GHSA-58g3-37cc-r74w"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java Runtime Environment","requires_auth":"none","summary":"Remote attackers can bypass Java sandbox restrictions via the logging API, potentially leading to privilege escalation and code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"jdk","vendor":"oracle"},{"product":"jre","vendor":"oracle"},{"product":"jdk","vendor":"sun"},{"product":"jre","vendor":"sun"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, 5.0 through Update 38, and 1.4.2_40 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2013-0428 and CVE-2013-0426.  NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to incorrect \"access control checks\" in the logging API that allow remote attackers to bypass Java sandbox restrictions.","ecosystems":[],"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":"Security feature bypass in n/a","id":"CVE-2013-0425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:jdk","products":["oracle:jdk","oracle:jre","sun:jdk","sun:jre"],"type":"security_feature_bypass","year":"2013"},"n_packages":0,"n_references":30,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2013-0426"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-0424"},"products":["n/a"],"published":"2013-02-02","related":[{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2012-4681","kev_date_added":"2022-03-03","published":"2012-08-28"},{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2012-1723","kev_date_added":"2022-03-03","published":"2012-06-16"},{"cvss_score":10,"headline":"Deserialization in n/a","id":"CVE-2015-4805","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4835","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4843","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4844","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4860","kev_date_added":null,"published":"2015-10-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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 Java sandbox restrictions via the logging API, potentially leading to privilege escalation and code execution.","url":"https://insights.sbomify.com/CVE-2013-0425/"}