{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21217 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21217 is a critical memory corruption 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-2022-21217 and fix it if it is affected.\n\nWhat it is: CVE-2022-21217 is a critical memory corruption 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: There is no known exploitation of CVE-2022-21217 in the wild and no public exploit code.\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-2022-21217/ (Markdown: https://insights.sbomify.com/CVE-2022-21217/index.md)","id":"CVE-2022-21217","markdown":"https://insights.sbomify.com/CVE-2022-21217/index.md","name":"CVE-2022-21217","record":{"aliases":["GHSA-v36c-pq4h-93xc"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink IP camera","requires_auth":"high_privilege","summary":"An attacker can trigger an out-of-bounds write in the Reolink camera's email test feature via a crafted HTTP request, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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-787","name":"Out-of-bounds Write"},{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"An out-of-bounds write vulnerability exists in the device TestEmail functionality of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted network request can lead to an out-of-bounds write. An attacker can send an HTTP request to trigger this vulnerability.","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":"Memory corruption in n/a","id":"CVE-2022-21217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"reolink:rlc-410w_firmware","products":["reolink:rlc-410w_firmware"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Intel(R) Trace Analyzer and Collector","id":"CVE-2022-21218"},"packages":[],"prev":{"headline":"Privilege escalation in Intel(R) Atom and Intel Xeon Scalable Processors","id":"CVE-2022-21216"},"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["n/a"]},"summary":"An attacker can trigger an out-of-bounds write in the Reolink camera's email test feature via a crafted HTTP request, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-21217/"}