{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-28372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28372 is a high-severity vulnerability in n/a, published on 14 Jul 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-28372 and fix it if it is affected.\n\nWhat it is: CVE-2022-28372 is a high-severity vulnerability in n/a, published on 14 Jul 2022. 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-2022-28372 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-2022-28372/ (Markdown: https://insights.sbomify.com/CVE-2022-28372/index.md)","id":"CVE-2022-28372","markdown":"https://insights.sbomify.com/CVE-2022-28372/index.md","name":"CVE-2022-28372","record":{"aliases":["GHSA-qf9q-2744-2xwj"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Verizon 5G Home","requires_auth":"none","summary":"Attackers can upload arbitrary firmware files to Verizon 5G Home devices via unvalidated RPC endpoints, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lvskihp_indoorunit_firmware","vendor":"verizon"},{"product":"lvskihp_outdoorunit_firmware","vendor":"verizon"}],"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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"On Verizon 5G Home LVSKIHP InDoorUnit (IDU) 3.4.66.162 and OutDoorUnit (ODU) 3.33.101.0 devices, the CRTC and ODU RPC endpoints provide a means of provisioning a firmware update for the device via crtc_fw_upgrade or crtcfwimage. The URL provided is not validated, and thus allows for arbitrary file upload to the device. This occurs in /lib/lua/luci/crtc.lua (IDU) and /lib/functions/wnc_jsonsh/wnc_crtc_fw.sh (ODU).","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":"File upload in n/a","id":"CVE-2022-28372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2022-28373"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-28371"},"products":["n/a"],"published":"2022-07-14","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-28369","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-28373","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-28371","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-28377","kev_date_added":null,"published":"2022-07-14"}],"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-03","vendors":["n/a"]},"summary":"Attackers can upload arbitrary firmware files to Verizon 5G Home devices via unvalidated RPC endpoints, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-28372/"}