{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-24054 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24054 is a critical command injection vulnerability in n/a, published on 21 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-24054 and fix it if it is affected.\n\nWhat it is: CVE-2020-24054 is a critical command injection vulnerability in n/a, published on 21 Aug 2020. 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-2020-24054 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-2020-24054/ (Markdown: https://insights.sbomify.com/CVE-2020-24054/index.md)","id":"CVE-2020-24054","markdown":"https://insights.sbomify.com/CVE-2020-24054/index.md","name":"CVE-2020-24054","record":{"aliases":["GHSA-r7c7-43gw-hcm5"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Moog EXO Series","requires_auth":"none","summary":"Attackers can execute arbitrary commands as root on Moog EXO Series units by bypassing input restrictions in the administration console.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exvf5c-2_firmware","vendor":"moog"},{"product":"exvp7c2-3_firmware","vendor":"moog"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"The administration console of the Moog EXO Series EXVF5C-2 and EXVP7C2-3 units features a 'statusbroadcast' command that can spawn a given process repeatedly at a certain time interval as 'root'. One of the limitations of this feature is that it only takes a path to a binary without arguments; however, this can be circumvented using special shell variables, such as '${IFS}'. As a result, an attacker can execute arbitrary commands as 'root' on the units.","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":"Command injection in n/a","id":"CVE-2020-24054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-24055"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-24053"},"products":["n/a"],"published":"2020-08-21","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-24051","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2020-24052","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-24053","kev_date_added":null,"published":"2020-08-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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands as root on Moog EXO Series units by bypassing input restrictions in the administration console.","url":"https://insights.sbomify.com/CVE-2020-24054/"}