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.
References
Link | Resource |
---|---|
https://github.com/fierceoj/ownklok | Exploit Third Party Advisory |
https://github.com/fierceoj/ownklok | Exploit Third Party Advisory |
Configurations
History
21 Nov 2024, 05:39
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/fierceoj/ownklok - Exploit, Third Party Advisory |
Information
Published : 2020-05-04 14:15
Updated : 2024-11-21 05:39
NVD link : CVE-2020-8791
Mitre link : CVE-2020-8791
CVE.ORG link : CVE-2020-8791
JSON object : View
Products Affected
oklok_project
- oklok
CWE
CWE-639
Authorization Bypass Through User-Controlled Key