2021-28372 | ThroughTek Kalay Platform UID entropy
|CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in ThroughTek Kalay Platform up to 2.0. It has been rated as problematic. Affected by this issue is an unknown code of the component UID Handler. The manipulation with an unknown input leads to a weak encryption vulnerability. Using CWE to declare the problem leads to CWE-331. Impacted is confidentiality. CVE summarizes:
ThroughTek’s Kalay Platform 2.0 network allows an attacker to impersonate an arbitrary ThroughTek (TUTK) device given a valid 20-byte uniquely assigned identifier (UID). This could result in an attacker hijacking a victim’s connection and forcing them into supplying credentials needed to access the victim TUTK device.
The weakness was disclosed 08/18/2021. The advisory is shared for download at fireeye.com. This vulnerability is handled as CVE-2021-28372 since 03/13/2021. The exploitation is known to be difficult. The attack needs to be initiated within the local network. A simple authentication is needed for exploitation. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.5
Status: Not defined
0-Day Time: 🔒
Use the official API to access entries easily!