| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Ovarro TBoxLT2, TBox MS-CPU32, TBox MS-CPU32-S2, TBox RM2 and TBox TG2. Affected is an unknown function. Performing a manipulation results in hard-coded key. This vulnerability is identified as CVE-2021-22644. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Ovarro TBoxLT2, TBox MS-CPU32, TBox MS-CPU32-S2, TBox RM2 and TBox TG2. This affects some unknown processing. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality. The summary by CVE is:
Ovarro TBox TWinSoft uses the custom hardcoded user “TWinSoft” with a hardcoded key.
The weakness was released 07/29/2022 as icsa-21-054-04. The advisory is shared at cisa.gov. This vulnerability is uniquely identified as CVE-2021-22644 since 01/05/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Upgrading eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 7.5
CNA Vector (ICS-CERT): 🔍
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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/05/2021 🔍07/29/2022 🔍
07/29/2022 🔍
04/17/2025 🔍
Sources
Advisory: icsa-21-054-04Status: Confirmed
CVE: CVE-2021-22644 (🔍)
GCVE (CVE): GCVE-0-2021-22644
GCVE (VulDB): GCVE-100-205281
Entry
Created: 07/29/2022 07:40Updated: 04/17/2025 21:08
Changes: 07/29/2022 07:40 (48), 08/28/2022 13:17 (11), 04/17/2025 21:08 (15)
Complete: 🔍
Cache ID: 216:F1C:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.