# CVE-2023-34625: Auth bypass in n/a

> Attackers can bypass authentication and open the digital lockbox by replaying intercepted Bluetooth Low Energy requests or extracting them from app logs.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 20 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-7vcc-qhc2-h2xw

## What is CVE-2023-34625?

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

### Official description

ShowMojo MojoBox Digital Lockbox 1.4 is vulnerable to Authentication Bypass. The implementation of the lock opening mechanism via Bluetooth Low Energy (BLE) is vulnerable to replay attacks. A malicious user is able to intercept BLE requests and replicate them to open the lock at any time. Alternatively, an attacker with physical access to the device on which the Android app is installed, can obtain the latest BLE messages via the app logs and use them for opening the lock.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Showmojo Mojobox Firmware.

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

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

## Is CVE-2023-34625 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34625 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34625 is a high-severity authentication bypass vulnerability in n/a, published on 20 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34625 exists.

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-2023-34625/ (Markdown: https://insights.sbomify.com/CVE-2023-34625/index.md)
```

## Sources

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

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