{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-28370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28370 is a high-severity code injection 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-28370 and fix it if it is affected.\n\nWhat it is: CVE-2022-28370 is a high-severity code injection 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-28370 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-28370/ (Markdown: https://insights.sbomify.com/CVE-2022-28370/index.md)","id":"CVE-2022-28370","markdown":"https://insights.sbomify.com/CVE-2022-28370/index.md","name":"CVE-2022-28370","record":{"aliases":["GHSA-j9q2-467q-5fww"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Verizon 5G Home ODU","requires_auth":"none","summary":"Attackers can install malicious firmware on Verizon 5G Home Outdoor Units due to missing cryptographic validation of update images.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"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-345","name":"Insufficient Verification of Data Authenticity"}],"description":"On Verizon 5G Home LVSKIHP OutDoorUnit (ODU) 3.33.101.0 devices, the RPC endpoint crtc_fw_upgrade provides a means of provisioning a firmware update for the device. /lib/functions/wnc_jsonsh/wnc_crtc_fw.sh has no cryptographic validation of the image, thus allowing an attacker to modify the installed firmware.","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":"Code injection in n/a","id":"CVE-2022-28370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-28371"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2022-28369"},"products":["n/a"],"published":"2022-07-14","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-28375","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-28374","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 install malicious firmware on Verizon 5G Home Outdoor Units due to missing cryptographic validation of update images.","url":"https://insights.sbomify.com/CVE-2022-28370/"}