{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21236 exists.","fix":"No fix has been published for CVE-2022-21236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21236 is a high-severity vulnerability in Reolink Rlc-410w Firmware, published on 28 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21236 and fix it if it is affected.\n\nWhat it is: CVE-2022-21236 is a high-severity vulnerability in Reolink Rlc-410w Firmware, published on 28 Jan 2022. 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-2022-21236 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-2022-21236/ (Markdown: https://insights.sbomify.com/CVE-2022-21236/index.md)","id":"CVE-2022-21236","markdown":"https://insights.sbomify.com/CVE-2022-21236/index.md","name":"CVE-2022-21236","record":{"aliases":["GHSA-98gj-54m7-m5m8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink security camera","requires_auth":"none","summary":"An attacker can send a specially crafted HTTP request to a Reolink camera to disclose sensitive information due to web server misconfiguration.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"rlc-410w_firmware","vendor":"reolink"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"},{"id":"CWE-219","name":"Storage of File with Sensitive Data Under Web Root"}],"description":"An information disclosure vulnerability exists due to a web server misconfiguration in the Reolink RLC-410W v3.0.0.136_20121102. A specially-crafted HTTP request can lead to a disclosure of sensitive information. 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":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2022-21236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"reolink:rlc-410w_firmware","products":["reolink:rlc-410w_firmware"],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Intel(R) NUCs","id":"CVE-2022-21237"},"packages":[],"prev":{"headline":"Command Injection","id":"CVE-2022-21235"},"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":"An attacker can send a specially crafted HTTP request to a Reolink camera to disclose sensitive information due to web server misconfiguration.","url":"https://insights.sbomify.com/CVE-2022-21236/"}