Account data disclosure via predictable barcode guessing
Published May 4, 2020 · Updated Aug 4, 2024
Information exposure in OKLOK 3.1.1 allows remote attackers to disclose users' email addresses and lock names via guessed barcodes. The add-lock workflow accepts predictable barcode strings and returns account data when a guess identifies an already-bound FB50 2.3 lock. No authentication or user interaction is required, and the documented consequence is limited to disclosure of the email address and lock name.
Summary
What happened
Information exposure in OKLOK 3.1.1 allows remote attackers to disclose users' email addresses and lock names via guessed barcodes. The add-lock workflow accepts predictable barcode strings and returns account data when a guess identifies an already-bound FB50 2.3 lock. No authentication or user interaction is required, and the documented consequence is limited to disclosure of the email address and lock name.
The record
- CVE
- CVE-2020-8792
- Published
- May 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1589.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo