Tinycontrol LAN Controller vLK up to 1.58a lk3_settings.bin password in config
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Tinycontrol LAN Controller vLK up to 1.58a. This vulnerability affects unknown code of the file lk3_settings.bin. Executing a manipulation can lead to password in config. This vulnerability is handled as CVE-2023-53739. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability was found in Tinycontrol LAN Controller vLK up to 1.58a. It has been declared as problematic. This vulnerability affects an unknown code block of the file lk3_settings.bin. The manipulation with an unknown input leads to a password in config vulnerability. The CWE definition for the vulnerability is CWE-260. The product stores a password in a configuration file that might be accessible to actors who do not know the password. As an impact it is known to affect confidentiality. CVE summarizes:
Tinycontrol LAN Controller v3 LK3 version 1.58a contains an unauthenticated vulnerability that allows remote attackers to download configuration backup files containing sensitive credentials. Attackers can retrieve the lk3_settings.bin file and extract base64-encoded user and admin passwords without authentication.
The weakness was released by Gjoko Krstic as 51731. The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2023-53739 since 12/07/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1552.001.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (51731). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Password in configCWE: CWE-260 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/07/2025 CVE reserved12/10/2025 Advisory disclosed
12/10/2025 VulDB entry created
12/10/2025 VulDB entry last update
Sources
Advisory: 51731Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2023-53739 (🔒)
GCVE (CVE): GCVE-0-2023-53739
GCVE (VulDB): GCVE-100-335536
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/10/2025 07:58Changes: 12/10/2025 07:58 (70)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.