{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45467 exists.","fix":"No fix has been published for CVE-2025-45467 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45467 is a high-severity vulnerability in n/a, published on 25 Jul 2025. 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-2025-45467 and fix it if it is affected.\n\nWhat it is: CVE-2025-45467 is a high-severity vulnerability in n/a, published on 25 Jul 2025. 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-2025-45467 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-2025-45467/ (Markdown: https://insights.sbomify.com/CVE-2025-45467/index.md)","id":"CVE-2025-45467","markdown":"https://insights.sbomify.com/CVE-2025-45467/index.md","name":"CVE-2025-45467","record":{"aliases":["GHSA-56gq-m2m7-qc85"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Unitree Go1 robot","requires_auth":"none","summary":"Attackers can bypass firmware integrity checks using MD5 collisions to install malicious firmware on Unitree Go1 robots via network interfaces.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"go1_firmware","vendor":"unitree"}],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Unitree Go1 \u003c= Go1_2022_05_11 is vulnerable to Insecure Permissions as the firmware update functionality (via Wi-Fi/Ethernet) implements an insecure verification mechanism that solely relies on MD5 checksums for firmware integrity validation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-06-24","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-24T06:58:40Z","kind":"github_poc","ref":"https://github.com/zgsnj123/CVE-2025-45467","stars":1,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-45467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-45468"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-45466"},"products":["n/a"],"published":"2025-07-25","related":[{"cvss_score":8.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-45466","kev_date_added":null,"published":"2025-07-25"},{"cvss_score":6.6,"headline":"Unitree Go1 Robot Dog Backdoor Control Channel","id":"CVE-2025-2894","kev_date_added":null,"published":"2025-03-28"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-25","vendors":["n/a"]},"summary":"Attackers can bypass firmware integrity checks using MD5 collisions to install malicious firmware on Unitree Go1 robots via network interfaces.","url":"https://insights.sbomify.com/CVE-2025-45467/"}