CVE-2025-60017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnitree Go2, G1, H1, and B2 devices through 2025-09-20 allow root OS command injection via the hostapd_restart.sh wifi_ssid or wifi_pass parameter (within restart_wifi_ap and restart_wifi_sta).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnitree robot devices (Go2, G1, H1, B2) contain an OS command injection vulnerability in the hostapd_restart.sh script. The wifi_ssid and wifi_pass parameters passed to the restart_wifi_ap and restart_wifi_sta functions are not sanitized before being used in shell command execution, allowing arbitrary OS commands to be injected and executed with root privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Unitree robot modelCheck the device label, documentation, or system information to confirm if it is a Go2, G1, H1, or B2 model.Affected if The device is any of these four models (Go2, G1, H1, or B2).
-
Locate the hostapd_restart.sh scriptAccess the device filesystem (via SSH or debug interface if available) and search for the hostapd_restart.sh script, typically found in /etc/scripts/ or similar paths.Affected if The script exists on the device, indicating the wifi restart functionality is present.
-
Verify network exposure of wifi configuration interfacesCheck if the device wifi configuration APIs or web interfaces are accessible from untrusted networks by reviewing network firewall rules, port scans, or interface bindings.Affected if The wifi configuration interfaces (HTTP/HTTPS endpoints for restart_wifi_ap or restart_wifi_sta) are exposed to network segments accessible by untrusted users.
-
Confirm authentication requirements for wifi functionsReview access controls on the wifi configuration endpoints to determine if authentication is enforced and whether attacker authentication is feasible in your deployment.Affected if The wifi_ssid and wifi_pass parameters can be supplied by an authenticated attacker, or if authentication is weak/missing, allowing command injection.
You are affected if you operate a Unitree Go2, G1, H1, or B2 robot with the hostapd_restart.sh script present and its wifi configuration interface is accessible to authenticated attackers on your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates when available; otherwise, implement input validation on the wifi_ssid and wifi_pass parameters to sanitize special shell characters before passing to shell commands. Network segmentation can reduce attack surface for unauthenticated exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data