CVE-2017-17831

CVE-2017-17831 is a high-severity vulnerability in Git Large File Storage Project Git Large File Storage with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-20.

Key facts

Description

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.

Frequently asked questions

What is CVE-2017-17831?
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.
How severe is CVE-2017-17831?
CVE-2017-17831 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-17831 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-17831?
CVE-2017-17831 affects Git Large File Storage Project Git Large File Storage. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-17831?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-17831 published?
CVE-2017-17831 was published on 2017-12-21 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Git Large File Storage Project Git Large File Storage

All CVEs affecting Git Large File Storage Project Git Large File Storage →

Other CWE-20 (Improper Input Validation) vulnerabilities

Browse all CWE-20 (Improper Input Validation) vulnerabilities →