CVE-2017-17831
N/A
Published: December 21, 2017 at 06:00 AM UTC
Updated: June 17, 2026 at 01:11 AM UTC
1 product affected across 1 vendorGit Large File Storage
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 4%
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v < 2.1.1
Affected range stops below 2.1.1, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (5)
x_refsource_MISCExploitThird Party Advisory
Source: [email protected]
http://blog.recurity-labs.com/2017-08-10/scm-vulnsVDB Entryx_refsource_BIDThird Party Advisory
Source: [email protected]
http://www.securityfocus.com/bid/102926x_refsource_CONFIRMThird Party Advisory
Source: [email protected]
https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.htmlx_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://github.com/git-lfs/git-lfs/pull/2242x_refsource_MISCRelease NotesThird Party Advisory
Source: [email protected]
https://github.com/git-lfs/git-lfs/releases/tag/v2.1.1Quick Info
StatusMODIFIED
CWE
CWE-20
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card