# CVE-2022-29948: Auth bypass in n/a

> Physical replacement of the microcontroller allows bypassing authentication to read encrypted data from Lepin EP-KP001 flash drives.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 10 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cxgm-7388-fwmx

## What is CVE-2022-29948?

CVE-2022-29948 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to an insecure design, the Lepin EP-KP001 flash drive through KP001_V19 is vulnerable to an authentication bypass attack that enables an attacker to gain access to the stored encrypted data. Normally, the encrypted disk partition with this data is unlocked by entering the correct passcode (6 to 14 digits) via the keypad and pressing the Unlock button. This authentication is performed by an unknown microcontroller. By replacing this microcontroller on a target device with one from an attacker-controlled Lepin EP-KP001 whose passcode is known, it is possible to successfully unlock the target device and read the stored data in cleartext.

## Which versions are affected by CVE-2022-29948?

It affects 1 product.


Products: Lepin Ep-Kp001 Project Lepinep-Kp001 Firmware.

## How do I fix CVE-2022-29948?

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

## Is CVE-2022-29948 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29948 and fix it if it is affected.

What it is: CVE-2022-29948 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Jun 2022. 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-2022-29948 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-2022-29948/ (Markdown: https://insights.sbomify.com/CVE-2022-29948/index.md)
```

## Sources

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

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