{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-9392 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9392 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9392 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9392 and fix it if it is affected.\n\nWhat it is: CVE-2017-9392 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-9392 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-2017-9392/ (Markdown: https://insights.sbomify.com/CVE-2017-9392/index.md)","id":"CVE-2017-9392","markdown":"https://insights.sbomify.com/CVE-2017-9392/index.md","name":"CVE-2017-9392","record":{"aliases":["GHSA-rxm4-5c6c-f64m"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vera home automation controller","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code on Vera home automation devices by sending a crafted UPnP request with an overly long resolution parameter.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"veraedge_firmware","vendor":"getvera"},{"product":"veralite_firmware","vendor":"getvera"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered on Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. The device provides UPnP services that are available on port 3480 and can also be accessed via port 80 using the url \"/port_3480\". It seems that the UPnP services provide \"request_image\" as one of the service actions for a normal user to retrieve an image from a camera that is controlled by the controller. It seems that the \"res\" (resolution) parameter passed in the query string is not sanitized and is stored on the stack which allows an attacker to overflow the buffer. The function \"LU::Generic_IP_Camera_Manager::REQ_Image\" is activated when the lu_request_image is passed as the \"id\" parameter in the query string. This function then calls \"LU::Generic_IP_Camera_Manager::GetUrlFromArguments\". This function retrieves all the parameters passed in the query string including \"res\" and then uses the value passed in it to fill up buffer using the sprintf function. However, the function in this case lacks a simple length check and as a result an attacker who is able to send more than 184 characters can easily overflow the values stored on the stack including the $RA value and thus execute code on the device.","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-2017-9392","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in Identity Manager","id":"CVE-2017-9393"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-9391"},"products":["n/a"],"published":"2019-06-17","related":[{"cvss_score":9.9,"headline":"Server-side request forgery in n/a","id":"CVE-2017-9383","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2017-9385","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-9381","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9384","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9388","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2017-9389","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9391","kev_date_added":null,"published":"2019-06-17"}],"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-05","vendors":["n/a"]},"summary":"An attacker can execute arbitrary code on Vera home automation devices by sending a crafted UPnP request with an overly long resolution parameter.","url":"https://insights.sbomify.com/CVE-2017-9392/"}