Tridactyl up to 1.15.x Key Event Fake key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Tridactyl up to 1.15.x. This affects an unknown part of the component Key Event Handler. Performing a manipulation results in key management (Fake). This vulnerability is identified as CVE-2019-1020004. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Tridactyl up to 1.15.x. It has been classified as critical. This affects some unknown processing of the component Key Event Handler. The manipulation with an unknown input leads to a key management vulnerability (Fake). CWE is classifying the issue as CWE-320. This is going to have an impact on integrity. The summary by CVE is:
Tridactyl before 1.16.0 allows fake key events.
The weakness was released 07/29/2019. This vulnerability is uniquely identified as CVE-2019-1020004 since 07/26/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Upgrading to version 1.16.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Name: FakeClass: Key management / Fake
CWE: 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: 🔍
Upgrade: Tridactyl 1.16.0
Timeline
07/26/2019 🔍07/29/2019 🔍
07/30/2019 🔍
11/13/2023 🔍
Sources
Product: github.comAdvisory: GHSA-7qr7-93pf-hr8f
Status: Not defined
CVE: CVE-2019-1020004 (🔍)
GCVE (CVE): GCVE-0-2019-1020004
GCVE (VulDB): GCVE-100-138921
Entry
Created: 07/30/2019 08:21Updated: 11/13/2023 14:54
Changes: 07/30/2019 08:21 (36), 07/15/2020 09:12 (17), 11/13/2023 14:54 (5)
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.