{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0923 exists.","fix":"No fix has been published for CVE-2011-0923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-0923 is a critical code injection vulnerability in n/a, published on 9 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-0923 and fix it if it is affected.\n\nWhat it is: CVE-2011-0923 is a critical code injection vulnerability in n/a, published on 9 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0923 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-2011-0923/ (Markdown: https://insights.sbomify.com/CVE-2011-0923/index.md)","id":"CVE-2011-0923","markdown":"https://insights.sbomify.com/CVE-2011-0923/index.md","name":"CVE-2011-0923","record":{"aliases":["GHSA-px66-r9g5-2c75"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"HP Data Protector","requires_auth":"none","summary":"Remote attackers can execute arbitrary Perl code in HP Data Protector clients due to improper validation of EXEC_CMD arguments.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"data_protector","vendor":"hp"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The client in HP Data Protector does not properly validate EXEC_CMD arguments, which allows remote attackers to execute arbitrary Perl code via a crafted command, related to the \"local bin directory.\"","ecosystems":[],"exploits":{"exploitdb":5,"first_seen":"2011-02-07","github_poc":0,"max_poc_stars":null,"metasploit":2,"nuclei":0,"refs":[{"date":"2011-02-07","kind":"metasploit","ref":"auxiliary/admin/hp/hp_data_protector_cmd","stars":null,"title":"HP Data Protector 6.1 EXEC_CMD Command Execution"},{"date":"2011-02-07","kind":"metasploit","ref":"exploit/linux/misc/hp_data_protector_cmd_exec","stars":null,"title":"HP Data Protector 6 EXEC_CMD Remote Code Execution"},{"date":"2011-05-28","kind":"exploitdb","ref":"17339","stars":null,"title":"HP Data Protector Client 6.11 - 'EXEC_CMD' Remote Code Execution"},{"date":"2011-08-05","kind":"exploitdb","ref":"17614","stars":null,"title":"HP Data Protector (HP-UX) - Remote Shell"},{"date":"2011-08-10","kind":"exploitdb","ref":"17648","stars":null,"title":"HP Data Protector (Linux) - Remote Command Execution"},{"date":"2012-02-25","kind":"exploitdb","ref":"18521","stars":null,"title":"HP Data Protector 6.1 - EXEC_CMD Remote Code Execution (Metasploit)"},{"date":"2013-08-07","kind":"exploitdb","ref":"27400","stars":null,"title":"HP Data Protector - Remote Command Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2011-0923","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2011"},"n_packages":0,"n_references":9,"next":{"headline":"Code injection in n/a","id":"CVE-2011-0924"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2011-0922"},"products":["n/a"],"published":"2011-02-09","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2011-0921","kev_date_added":null,"published":"2011-02-09"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2011-0922","kev_date_added":null,"published":"2011-02-09"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2011-0924","kev_date_added":null,"published":"2011-02-09"},{"cvss_score":9.8,"headline":"Memory corruption in Data Protector","id":"CVE-2017-5807","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-2004","kev_date_added":null,"published":"2016-04-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2016-2005","kev_date_added":null,"published":"2016-04-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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-08-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary Perl code in HP Data Protector clients due to improper validation of EXEC_CMD arguments.","url":"https://insights.sbomify.com/CVE-2011-0923/"}