From oss-security mailing list: As mentioned in early messages to oss-sec, I've inherited maintainership of the cgit codebase and am gradually auditing it. Today I found a nasty directory traversal: http://somehost/?url=/somerepo/about/../../../../etc/passwd This should be pretty straightforward to categorize. Exploitation looks like: http://data.zx2c4.com/cgit-directory-traversal.png I've committed a fix for it here: http://git.zx2c4.com/cgit/commit/?h=wip&id=babf94e04e74123eb658a823213c062663cdadd6 And this fix will be in the master branch and a new release will be made soon. Cgit by default is not vulnerable to this, and the vulnerability only exists when a user has configured cgit to use a readme file from a filesystem filepath instead of from the git repo itself. Until a release is made, administrators are urged to disable reading the readme file from a filepath, if currently enabled.
This was assigned CVE-2013-2117 as per: http://seclists.org/oss-sec/2013/q2/414
This is fixed in upstream 0.9.2 release: http://lists.zx2c4.com/pipermail/cgit/2013-May/001394.html
Created cgit tracking bugs for this issue Affects: fedora-all [bug 967661] Affects: epel-all [bug 967662]
cgit-0.9.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
cgit-0.9.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
cgit-0.9.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
cgit-0.9.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
cgit-0.9.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.