{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40412 exists.","fix":"No fix has been published for CVE-2021-40412 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-40412 is a critical command injection vulnerability in Reolink Rlc-410w Firmware, published on 28 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-40412 and fix it if it is affected.\n\nWhat it is: CVE-2021-40412 is a critical command injection vulnerability in Reolink Rlc-410w Firmware, published on 28 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40412 exists.\n\nAffected product: Reolink Rlc-410w Firmware. 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-2021-40412/ (Markdown: https://insights.sbomify.com/CVE-2021-40412/index.md)","id":"CVE-2021-40412","markdown":"https://insights.sbomify.com/CVE-2021-40412/index.md","name":"CVE-2021-40412","record":{"aliases":["GHSA-8hcx-pw9g-w24x"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink IP camera","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary OS commands via the SetDevName API due to improper validation of the device name parameter.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"rlc-410w_firmware","vendor":"reolink"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An OScommand injection vulnerability exists in the device network settings functionality of reolink RLC-410W v3.0.0.136_20121102. At [8] the devname variable, that has the value of the name parameter provided through the SetDevName API, is not validated properly. This would lead to an OS command injection.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2021-40412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"reolink:rlc-410w_firmware","products":["reolink:rlc-410w_firmware"],"type":"command_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2021-40413"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2021-40411"},"products":["n/a"],"published":"2022-01-28","related":[{"cvss_score":9.1,"headline":"Reolink RLC-410W IP Camera OS Command Injection Vulnerability","id":"CVE-2021-40407","kev_date_added":"2024-12-18","published":"2022-01-28"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2021-40419","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2022-21796","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2021-40408","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2021-40409","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2021-40410","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2021-40411","kev_date_added":null,"published":"2022-01-28"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["n/a"]},"summary":"Attackers can execute arbitrary OS commands via the SetDevName API due to improper validation of the device name parameter.","url":"https://insights.sbomify.com/CVE-2021-40412/"}