{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-5001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2012-5001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-5001 is a high-severity vulnerability in n/a, published on 19 Sep 2012. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2012-5001 and fix it if it is affected.\n\nWhat it is: CVE-2012-5001 is a high-severity vulnerability in n/a, published on 19 Sep 2012. It can be exploited over the network.\nExploitation: There is no known exploitation of CVE-2012-5001 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2012-5001/ (Markdown: https://insights.sbomify.com/CVE-2012-5001/index.md)","id":"CVE-2012-5001","markdown":"https://insights.sbomify.com/CVE-2012-5001/index.md","name":"CVE-2012-5001","record":{"aliases":["GHSA-53xx-pxgc-j8qv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Network Node Manager","requires_auth":"unknown","summary":"Remote attackers can cause denial of service and potentially execute arbitrary code in Hitachi JP1/Cm2/Network Node Manager i.","user_interaction":"unknown","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jp1\\/cm2\\/network_node_manager","vendor":"hitachi"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Multiple unspecified vulnerabilities in Hitachi JP1/Cm2/Network Node Manager i before 09-50-03 allow remote attackers to cause a denial of service and possibly execute arbitrary code via unspecified vectors.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2012-5001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2012"},"n_packages":0,"n_references":6,"next":{"headline":"Memory corruption in n/a","id":"CVE-2012-5002"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2012-5000"},"products":["n/a"],"published":"2012-09-19","related":[],"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 cause denial of service and potentially execute arbitrary code in Hitachi JP1/Cm2/Network Node Manager i.","url":"https://insights.sbomify.com/CVE-2012-5001/"}