navigation bar left navigation bar right

navigation left tab Advisories navigation right tab
navigation left tab Research navigation right tab
navigation left tab Forums navigation right tab
navigation left tab Create Profile navigation right tab
navigation left tab Our Commitment navigation right tab
Advisories by Product
Advisories by Vendor
Report Vulnerability
Insecure Library Loading
Not critical

gitolite Security Bypass Weaknesses


Release Date:  2010-04-27    Last Update:  2010-05-05    Views:  3,370

Secunia Advisory SA39587


You need to log in to view this


You need to log in to view this

Solution Status:

You need to log in to view this


You need to log in to view this

CVE Reference(s):

You need to log in to view this


Some weaknesses have been reported in gitolite, which can be exploited by malicious users to bypass certain security restrictions

You need to log in to the Secunia Community to view the full description of this advisory

If you are not a member of the Secunia community, you can sign up here for free.

Do you have additional information related to this advisory?

Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this information to

Subject: gitolite Security Bypass Weaknesses

User Message
sitaramc RE: gitolite Security Bypass Weaknesses
Member 3rd May, 2010 18:29
Score: 3
Posts: 1
User Since: 3rd May 2010
System Score: N/A
Location: IN
Last edited on 3rd May, 2010 18:29

May I ask who sent in this advisory?

Item 1 in your list is *not yet* part of the stated purpose of gitolite. Originally there was no separation between admin and shell access and it is only recently that I have started slowly moving towards making that separation.

In short, only item 2 is valid, and therefore only is a *required* security fix.

I assume that the wording in *my* own commits is partly the reason. While I will be more careful in future, I still would like to know who sent this in so I can explain/elaborate on this issue if needed.

Put another way, there's a modest reward for security bugs in the README. Only the issue fixed by qualifies for that reward :-)



Was this reply relevant?


You must be logged in to post a comment.

 Products Solutions Customers Partner Resources Company
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
Technology Partners
 About us

Secunia is a member of FIRST Secunia is a member of EDUcause Secunia is a member of The Open Group Secunia is a member of FS-ISAC
Secunia © 2002-2015 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer
follow Secunia on Facebook follow Secunia on Twitter follow Secunia on LinkedIn follow Secunia on YouTube follow Secunia Xing follow Secunias RSS feed follow Secunia on Google+