| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in yadm 1.10.0. Affected by this vulnerability is an unknown functionality of the component git Clone Command. Such manipulation leads to race condition (Key). This vulnerability is traded as CVE-2017-11353. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in yadm 1.10.0. Affected by this issue is an unknown functionality of the component git Clone Command. The manipulation with an unknown input leads to a race condition vulnerability (Key). Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is confidentiality. CVE summarizes:
yadm (yet another dotfile manager) 1.10.0 has a race condition related to mishandling of a "git clone" command, which potentially allows access to SSH and PGP keys.
The bug was discovered 07/14/2017. The weakness was shared 07/17/2017 (Website). The advisory is shared for download at bugs.debian.org. This vulnerability is handled as CVE-2017-11353 since 07/16/2017. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
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: KeyClass: Race condition / Key
CWE: CWE-362
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/14/2017 🔍07/16/2017 🔍
07/17/2017 🔍
07/17/2017 🔍
07/18/2017 🔍
12/13/2022 🔍
Sources
Advisory: 74Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-11353 (🔍)
GCVE (CVE): GCVE-0-2017-11353
GCVE (VulDB): GCVE-100-103664
Entry
Created: 07/18/2017 09:11Updated: 12/13/2022 07:04
Changes: 07/18/2017 09:11 (56), 10/26/2019 17:16 (2), 12/13/2022 07:04 (3)
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.