GitHub Git LFS up to 2.1.0 Config File Hostname input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in GitHub Git LFS up to 2.1.0. This issue affects some unknown processing of the component Config File. Such manipulation as part of Hostname leads to input validation. This vulnerability is uniquely identified as CVE-2017-17831. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in GitHub Git LFS up to 2.1.0 (Bug Tracking Software). Affected by this issue is an unknown functionality of the component Config File. The manipulation as part of a Hostname leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes:
GitHub Git LFS before 2.1.1 allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash character in the hostname, located on a "url =" line in a .lfsconfig file within a repository.
The bug was discovered 12/21/2017. The weakness was disclosed 12/21/2017 (Website). The advisory is shared for download at blog.recurity-labs.com. This vulnerability is handled as CVE-2017-17831 since 12/21/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 scanner Nessus provides a plugin with the ID 106870 (Atlassian SourceTree 0.5.1.0 < 2.4.7.0 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370786 (Sourcetree for macOS and Windows Git LFS Arbitrary Command Execution Vulnerability).
Upgrading to version 2.1.1 eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (106870) and SecurityFocus (BID 102926†). The entries VDB-110335, VDB-112474 and VDB-112475 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Input validationCWE: CWE-20
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 |
Nessus ID: 106870
Nessus Name: Atlassian SourceTree 0.5.1.0 < 2.4.7.0 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Git LFS 2.1.1
Patch: github.com
Timeline
12/21/2017 🔍12/21/2017 🔍
12/21/2017 🔍
12/21/2017 🔍
12/21/2017 🔍
01/24/2018 🔍
01/24/2018 🔍
02/16/2018 🔍
01/18/2023 🔍
Sources
Advisory: blog.recurity-labs.comResearcher: ZhangTianqi @ Tophant
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-17831 (🔍)
GCVE (CVE): GCVE-0-2017-17831
GCVE (VulDB): GCVE-100-110972
SecurityFocus: 102926
See also: 🔍
Entry
Created: 12/21/2017 14:07Updated: 01/18/2023 16:47
Changes: 12/21/2017 14:07 (72), 12/28/2019 10:46 (3), 01/27/2021 17:32 (4), 01/18/2023 16:47 (4)
Complete: 🔍
Cache ID: 216:6BB:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.