# CVE-2019-13953: Auth bypass in n/a

> Attackers can bypass Bluetooth authentication on YI M1 cameras to leak photos and remotely control recording functions.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cc2f-p92p-prhw

## What is CVE-2019-13953?

CVE-2019-13953 is a high-severity authentication bypass vulnerability in n/a, published on 6 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable authentication bypass vulnerability exists in the Bluetooth Low Energy (BLE) authentication module of YI M1 Mirrorless Camera V3.2-cn. An attacker can send a set of BLE commands to trigger this vulnerability, resulting in sensitive data leakage (e.g., personal photos). An attacker can also control the camera to record or take a picture after bypassing authentication.

## Which versions are affected by CVE-2019-13953?

It affects 1 product.


Products: Xiaoyi Yi M1 Mirrorless Camera Firmware.

## How do I fix CVE-2019-13953?

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

## Is CVE-2019-13953 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13953 and fix it if it is affected.

What it is: CVE-2019-13953 is a high-severity authentication bypass vulnerability in n/a, published on 6 Sep 2019. 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-2019-13953 in the wild and no public exploit code.

Affected product: n/a. 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-2019-13953/ (Markdown: https://insights.sbomify.com/CVE-2019-13953/index.md)
```

## Sources

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

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