CVE-2013-2117: Path Traversal
Published Aug 9, 2013
·Updated
Directory traversal vulnerability in the cgitparsereadme function in ui-summary.c in cgit before 0.9.2, when a readme file is set to a filesystem path, allows remote attackers to read arbitrary files via a .. (dot dot) in the url parameter.
Affected Software
29 affected components
Jason A Donenfeld Cgit<=0.9.1
Lars Hjemli Cgit=0.1
Lars Hjemli Cgit=0.2
Lars Hjemli Cgit=0.3
Lars Hjemli Cgit=0.4
Lars Hjemli Cgit=0.5
Lars Hjemli Cgit=0.6
Lars Hjemli Cgit=0.6.1
Lars Hjemli Cgit=0.6.2
Lars Hjemli Cgit=0.6.3
Lars Hjemli Cgit=0.7
Lars Hjemli Cgit=0.7.1
Lars Hjemli Cgit=0.7.2
Lars Hjemli Cgit=0.8
Lars Hjemli Cgit=0.8.1
Lars Hjemli Cgit=0.8.1.1
Lars Hjemli Cgit=0.8.2
Lars Hjemli Cgit=0.8.2.1
Lars Hjemli Cgit=0.8.2.2
Lars Hjemli Cgit=0.8.3
Lars Hjemli Cgit=0.8.3.1
Lars Hjemli Cgit=0.8.3.2
Lars Hjemli Cgit=0.8.3.3
Lars Hjemli Cgit=0.8.3.4
Lars Hjemli Cgit=0.8.3.5
Lars Hjemli Cgit=0.9
Lars Hjemli Cgit=0.9.0.1
Lars Hjemli Cgit=0.9.0.2
Lars Hjemli Cgit=0.9.0.3
Event History
Aug 9, 2013
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-2117?
CVE-2013-2117 has a medium severity rating due to its potential to allow unauthorized access to system files.
2
How do I fix CVE-2013-2117?
To fix CVE-2013-2117, upgrade to cgit version 0.9.2 or later.
3
What types of attacks can exploit CVE-2013-2117?
CVE-2013-2117 can be exploited through directory traversal attacks via manipulated URL parameters.
4
Which versions of cgit are affected by CVE-2013-2117?
CVE-2013-2117 affects all cgit versions prior to 0.9.2.
5
Can CVE-2013-2117 lead to data breaches?
Yes, CVE-2013-2117 can potentially lead to data breaches by exposing sensitive files to unauthorized users.