Security readout for executives and security teams
Plain-English summary
CVE-2023-34625 describes an authentication bypass in ShowMojo MojoBox Digital Lockbox 1.4. The reported issue could let someone reopen a lock by replaying previously captured Bluetooth Low Energy traffic, or by obtaining recent BLE messages from Android app logs with device access.
Executive priority
Treat this as high priority if these lockboxes protect customer property, vacant units, keys, or sensitive premises. The risk is physical unauthorized access, not just IT compromise.
Technical view
The sources describe a BLE replay weakness in the lock-opening flow. Captured authorization messages are reportedly reusable, so the lock does not appear to enforce freshness or nonces. The CVE record lists no CVSS, CWE, vendor fix, or affected CPE details beyond MojoBox Digital Lockbox 1.4.
Likely exposure
Exposure is most likely where MojoBox Digital Lockbox 1.4 units protect real estate, rental, or access-control assets. Organizations without a lockbox inventory may need vendor and facilities records to confirm deployment.
Exploitation context
No CISA KEV entry is cited, so active exploitation is not established. Public writeups and an exploit reference indicate technical feasibility, but the provided sources do not prove widespread abuse.
Researcher notes
Evidence is source-limited: no CVSS, CWE, patch status, or authoritative vendor advisory is included. The core issue is replayable BLE lock-opening traffic, with an alternate path through Android app logs when an attacker has device access.
Mitigation direction
- Check ShowMojo or vendor guidance for firmware, app, or replacement recommendations.
- Inventory all MojoBox Digital Lockbox 1.4 deployments and prioritize exposed locations.
- Remove affected units from high-risk or unsupervised access points until remediated.
- Protect Android app devices from physical access and review log exposure.
- Add compensating physical monitoring where affected units must remain deployed.
Validation and detection
- Confirm whether MojoBox Digital Lockbox 1.4 is used in any facility or property workflow.
- Review procurement, facilities, and vendor records for model and version evidence.
- Check Android app devices for unnecessary log retention or exposed BLE message data.
- Ask the vendor whether available updates address replay resistance and app logging.
- Document affected locations and business owners for remediation tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-34625 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.