CVE-2022-2675
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 · uneditedUsing off-the-shelf commodity hardware, the Unitree Go 1 robotics platform version H0.1.7 and H0.1.9 (using firmware version 0.1.35) can be powered down by an attacker within normal RF range without authentication. Other versions may be affected, such as the A1.
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 · moderate confidenceThe Unitree Go 1 robotics platform (versions H0.1.7 and H0.1.9 with firmware 0.1.35, possibly A1) contains an authentication bypass vulnerability in its RF communication protocol. An attacker within normal wireless range can transmit a power-off command using commodity hardware without any authentication, causing immediate denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.1.35< 0.1.35CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Go 1 model variantLocate the model number on the robot body or documentation. The affected models are H0.1.7, H0.1.9, and possibly A1 variants.Affected if The model is Unitree Go 1 H0.1.7, H0.1.9, or A1.
-
Check the installed firmware versionAccess the robot's admin interface or use the Unitree companion app to view firmware details. The firmware version is typically listed in system settings or the diagnostic screen.Affected if The firmware version is 0.1.35 or earlier (any version less than 0.1.35).
-
Verify if RF remote control is enabledCheck the robot's wireless settings through the control app or physical receiver status LED. Confirm that the 2.4GHz remote receiver is paired and active.Affected if RF remote control functionality is currently enabled and the receiver is paired.
-
Confirm power-off via RF is functionalTest whether the remote control power button can turn off the robot. Observe if the robot responds to power-off commands from the remote without any authentication prompt.Affected if The robot can be powered off using the RF remote without any authentication or security verification.
You are affected if you have a Unitree Go 1 model H0.1.7, H0.1.9, or A1 with firmware version 0.1.35 or lower, and RF remote control is enabled.
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 data0.1.35
Implement authentication and encryption for all RF commands, or disable the unauthenticated power-off functionality. Update firmware when available.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2675 — 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-2022-2675 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