{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-28377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28377 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-28377 and fix it if it is affected.\n\nWhat it is: CVE-2022-28377 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-28377 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-28377/ (Markdown: https://insights.sbomify.com/CVE-2022-28377/index.md)","id":"CVE-2022-28377","markdown":"https://insights.sbomify.com/CVE-2022-28377/index.md","name":"CVE-2022-28377","record":{"aliases":["GHSA-6hxh-v9xw-6688"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Verizon 5G Home","requires_auth":"none","summary":"Attackers can derive static RPC credentials from the device MAC address to gain unauthorized access to Verizon 5G Home units.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"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:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"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 rely on a static account username/password for access control. This password can be generated via a binary included in the firmware, after ascertaining the MAC address of the IDU's base Ethernet interface, and adding the string DEVICE_MANUFACTURER='Wistron_NeWeb_Corp.' to /etc/device_info to replicate the host environment. This occurs in /etc/init.d/wnc_factoryssidkeypwd (IDU).","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":"Hardcoded credentials in n/a","id":"CVE-2022-28377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site Scripting in craftcms/cms","id":"CVE-2022-28378"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-28376"},"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":"File upload in n/a","id":"CVE-2022-28372","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 derive static RPC credentials from the device MAC address to gain unauthorized access to Verizon 5G Home units.","url":"https://insights.sbomify.com/CVE-2022-28377/"}