{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2020-22002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-22002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-22002 is a high-severity server-side request forgery vulnerability in n/a, published on 29 Apr 2021. 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-22002 and fix it if it is affected.\n\nWhat it is: CVE-2020-22002 is a high-severity server-side request forgery vulnerability in n/a, published on 29 Apr 2021. 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-22002 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-22002/ (Markdown: https://insights.sbomify.com/CVE-2020-22002/index.md)","id":"CVE-2020-22002","markdown":"https://insights.sbomify.com/CVE-2020-22002/index.md","name":"CVE-2020-22002","record":{"aliases":["GHSA-92vr-3r9m-g89p"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SmartLAN/G/SI device","requires_auth":"none","summary":"Unauthenticated attackers can force the device to make arbitrary HTTP requests via the host parameter, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartliving_10100l_firmware","vendor":"inim"},{"product":"smartliving_10100lg3_firmware","vendor":"inim"},{"product":"smartliving_1050_firmware","vendor":"inim"},{"product":"smartliving_1050g3_firmware","vendor":"inim"},{"product":"smartliving_505_firmware","vendor":"inim"},{"product":"smartliving_515_firmware","vendor":"inim"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An Unauthenticated Server-Side Request Forgery (SSRF) vulnerability exists in Inim Electronics Smartliving SmartLAN/G/SI \u003c=6.x within the GetImage functionality. The application parses user supplied data in the GET parameter 'host' to construct an image request to the service through onvif.cgi. Since no validation is carried out on the parameter, an attacker can specify an external domain and force the application to make an HTTP request to an arbitrary destination host.","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":"Server-side request forgery in n/a","id":"CVE-2020-22002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2020-22007"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-22001"},"products":["n/a"],"published":"2021-04-29","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-21995","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-21992","kev_date_added":null,"published":"2021-04-29"}],"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":"Unauthenticated attackers can force the device to make arbitrary HTTP requests via the host parameter, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2020-22002/"}