{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27542 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27542 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27542 is a medium-severity command injection vulnerability in n/a, published on 25 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27542 and fix it if it is affected.\n\nWhat it is: CVE-2020-27542 is a medium-severity command injection vulnerability in n/a, published on 25 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-27542 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-27542/ (Markdown: https://insights.sbomify.com/CVE-2020-27542/index.md)","id":"CVE-2020-27542","markdown":"https://insights.sbomify.com/CVE-2020-27542/index.md","name":"CVE-2020-27542","record":{"aliases":["GHSA-f9cq-378f-9cj4"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IP camera","requires_auth":"none","summary":"An attacker can execute arbitrary commands on the camera by providing a malicious QR code during initial configuration.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cs-c2shw_firmware","vendor":"company"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/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":"Rostelecom CS-C2SHW 5.0.082.1 is affected by: Bash command injection. The camera reads configuration from QR code (including network settings). The static IP configuration from QR code is copied to the file /config/ip-static and after reboot data from this file is inserted into bash command (without any escaping). So bash injection is possible. Camera doesn't parse QR codes if it's already successfully configured. Camera is always rebooted after successful configuration via QR code.","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-27542","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of Service (DoS) in restify-paginate","id":"CVE-2020-27543"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2020-27541"},"products":["n/a"],"published":"2021-01-25","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-27539","kev_date_added":null,"published":"2021-01-25"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-27540","kev_date_added":null,"published":"2021-01-25"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2020-27541","kev_date_added":null,"published":"2021-01-25"}],"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":"An attacker can execute arbitrary commands on the camera by providing a malicious QR code during initial configuration.","url":"https://insights.sbomify.com/CVE-2020-27542/"}