CVE-2023-34625 json
ShowMojo MojoBox Digital Lockbox 1.4 is vulnerable to Authentication Bypass.
published 2023-07-20 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-38669
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- whid.ninja https://www.whid.ninja/blog/mojobox-yet-another-not-so-smartlock referenced PoC, tagged "exploit" by a source, unverified
- mandomat.github.io https://mandomat.github.io/2023-03-15-testing-mojobox-security/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- showmojo mojobox
Classification
- Weakness
-
- CWE-294 Authentication Bypass by Capture-replay
References
-
whid.ninja
/blog/mojobox-yet-another-not-so-smartlock
exploit, technical-description, third-party-advisory
-
mandomat.github.io
/2023-03-15-testing-mojobox-security/
exploit, technical-description, third-party-advisory
-
packetstormsecurity.com
/2307-exploits/mojobox14-replay.txt
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2023-34625
- NVD CVE-2023-34625
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.