# CVE-2023-3103: Authentication Bypass by Spoofing in Unitree Robotics A1

> A local attacker can bypass authentication to perform MITM attacks on the robot's video stream, potentially causing denial of service.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-798h-6rgp-73qq

## What is CVE-2023-3103?

CVE-2023-3103 is a high-severity authentication bypass vulnerability in Unitree Robotics A1, published on 22 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication bypass vulnerability, the exploitation of which could allow a local attacker to perform a Man-in-the-Middle (MITM) attack on the robot's camera video stream. In addition, if a MITM attack is carried out, it is possible to consume the robot's resources, which could lead to a denial-of-service (DOS) condition.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2023-3103?

It affects 1 product.


Products: Unitree A1 Firmware.

## How do I fix CVE-2023-3103?

No fix has been published for CVE-2023-3103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-3103 being exploited?

There is no known exploitation of CVE-2023-3103 in the wild and no public exploit code.

## Other vulnerabilities in Unitree Robotics A1

- [CVE-2023-3104](https://insights.sbomify.com/CVE-2023-3104/): Missing Authentication for Critical Function in Unitree Robotics A1 (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3103 and fix it if it is affected.

What it is: CVE-2023-3103 is a high-severity authentication bypass vulnerability in Unitree Robotics A1, published on 22 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3103 in the wild and no public exploit code.

Affected product: Unitree Robotics A1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3103/ (Markdown: https://insights.sbomify.com/CVE-2023-3103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3103
- OSV: https://osv.dev/vulnerability/CVE-2023-3103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3103/
Summaries are generated and may contain mistakes; the official description above is the record.
