{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48072 exists.","fix":"No fix has been published for CVE-2022-48072 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48072 is a high-severity command injection vulnerability in n/a, published on 27 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-48072 and fix it if it is affected.\n\nWhat it is: CVE-2022-48072 is a high-severity command injection vulnerability in n/a, published on 27 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48072 exists.\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-48072/ (Markdown: https://insights.sbomify.com/CVE-2022-48072/index.md)","id":"CVE-2022-48072","markdown":"https://insights.sbomify.com/CVE-2022-48072/index.md","name":"CVE-2022-48072","record":{"aliases":["GHSA-2968-6vjj-whq8"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Phicomm K2G router","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands on Phicomm K2G routers via the autoUpTime parameter in the automatic upgrade function.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"k2_firmware","vendor":"phicomm"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Phicomm K2G v22.6.3.20 was discovered to contain a command injection vulnerability via the autoUpTime parameter in the automatic upgrade function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2022-48072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-48073"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-48071"},"products":["n/a"],"published":"2023-01-27","related":[{"cvss_score":8.4,"headline":"Weak cryptography in Phicomm Routers","id":"CVE-2022-25219","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.1,"headline":"Weak cryptography in Phicomm Routers","id":"CVE-2022-25218","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2023-40796","kev_date_added":null,"published":"2023-08-25"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2022-48070","kev_date_added":null,"published":"2023-01-27"},{"cvss_score":7.8,"headline":"Hardcoded credentials in Phicomm Routers","id":"CVE-2022-25217","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-48071","kev_date_added":null,"published":"2023-01-27"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-28","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands on Phicomm K2G routers via the autoUpTime parameter in the automatic upgrade function.","url":"https://insights.sbomify.com/CVE-2022-48072/"}