{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2370 exists.","fix":"No fix has been published for CVE-2013-2370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2370 is a high-severity code injection vulnerability in n/a, published on 26 Jul 2013. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2013-2370 and fix it if it is affected.\n\nWhat it is: CVE-2013-2370 is a high-severity code injection vulnerability in n/a, published on 26 Jul 2013. It can be exploited over the network.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2370 exists.\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-2013-2370/ (Markdown: https://insights.sbomify.com/CVE-2013-2370/index.md)","id":"CVE-2013-2370","markdown":"https://insights.sbomify.com/CVE-2013-2370/index.md","name":"CVE-2013-2370","record":{"aliases":["GHSA-mx7x-r3cf-xwwh"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LoadRunner testing tool","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary code on HP LoadRunner installations, posing a significant risk to performance testing environments.","user_interaction":"unknown","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hp","cpe":[{"product":"loadrunner","vendor":"hp"}],"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":"Unspecified vulnerability in HP LoadRunner before 11.52 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1671.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2013-07-24","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2013-07-24","kind":"metasploit","ref":"exploit/windows/browser/hp_loadrunner_writefilebinary","stars":null,"title":"HP LoadRunner lrFileIOService ActiveX Remote Code Execution"},{"date":"2013-08-29","kind":"exploitdb","ref":"27939","stars":null,"title":"HP LoadRunner - lrFileIOService ActiveX Remote Code Execution (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2013-2370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-2371"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2013-2369"},"products":["n/a"],"published":"2013-07-26","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2015-2110","kev_date_added":null,"published":"2015-05-25"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2013-6213","kev_date_added":null,"published":"2014-04-19"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2013-4837","kev_date_added":null,"published":"2013-11-04"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2013-4838","kev_date_added":null,"published":"2013-11-04"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2013-4798","kev_date_added":null,"published":"2013-07-26"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2011-0272","kev_date_added":null,"published":"2011-01-18"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2010-1549","kev_date_added":null,"published":"2010-05-07"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on HP LoadRunner installations, posing a significant risk to performance testing environments.","url":"https://insights.sbomify.com/CVE-2013-2370/"}