| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in TCL 8.6.11. Affected by this vulnerability is an unknown functionality of the file nmakehlp.c. Performing a manipulation results in format string. This vulnerability is cataloged as CVE-2021-35331. There is no exploit available. The actual existence of this vulnerability is currently in question. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as critical, was found in TCL 8.6.11. This affects an unknown functionality of the file nmakehlp.c. The manipulation with an unknown input leads to a format string vulnerability. CWE is classifying the issue as CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 07/05/2021. The advisory is shared at core.tcl-lang.org. This vulnerability is uniquely identified as CVE-2021-35331. Technical details are known, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Format stringCWE: CWE-134 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/23/2021 🔍07/05/2021 🔍
07/05/2021 🔍
08/04/2024 🔍
Sources
Advisory: core.tcl-lang.orgStatus: Confirmed
Disputed: 🔍
CVE: CVE-2021-35331 (🔍)
GCVE (CVE): GCVE-0-2021-35331
GCVE (VulDB): GCVE-100-177969
Entry
Created: 07/05/2021 18:25Updated: 08/04/2024 03:35
Changes: 07/05/2021 18:25 (38), 07/09/2021 22:35 (5), 08/04/2024 03:35 (34)
Complete: 🔍
Cache ID: 216::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.