public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ivan Kanis <ivan.kanis@googlemail•com>
To: Git Mailing List <git@vger•kernel.org>
Subject: security flaw with smart http
Date: Fri, 22 Jun 2012 12:12:25 +0200 (7 hours, 36 minutes, 16 seconds ago)	[thread overview]
Message-ID: <87fw9ns0cp.fsf@kanis.fr> (raw)

Hi,

I think we found a security flaw with git http smart backend. We are
running git version 1.0.7.4 on our server. Adding random words after the
password and the authentication still succeeds. 

It's very easy to reproduce, say the username is ivan and the password
is the word secret:

% git pull
Username: ivan
Password: secretfoo
Already up to date.

Pull succeeds although the password is wrong! Can someone try to
reproduce with a more up to date git server?
-- 
Ivan Kanis
http://ivan.kanis.fr

             reply	other threads:[~2012-06-22 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 10:12 Ivan Kanis [this message]
2012-06-22 17:54 ` security flaw with smart http Shawn Pearce
2012-06-22 19:34   ` Junio C Hamano
2012-06-25 11:24     ` Philippe Vaucher
2012-06-25 12:59       ` Ivan Kanis
2012-06-25 13:10         ` Erik Faye-Lund
2012-06-28  7:35     ` Ivan Kanis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fw9ns0cp.fsf@kanis.fr \
    --to=ivan.kanis@googlemail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox