All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix buffer overflow in config parser
Date: Thu, 9 Apr 2009 01:15:17 +0200	[thread overview]
Message-ID: <200904090115.17609.markus.heidelberg@web.de> (raw)
In-Reply-To: <200904090058.42751.markus.heidelberg@web.de>

Markus Heidelberg, 09.04.2009:
> Thomas Jarosch, 09.04.2009:
> > Hello together,
> > 
> > attached is a small patch to fix a buffer overflow in config.c.
> > Patch is against git master's HEAD.
> > 
> > I didn't send this one inline as I wanted to
> > preserve the 1024+ byte long line.
> 
> You could send the patch inline and attach the example config.
> 
> > diff --git a/config.c b/config.c
> > index b76fe4c..a9c67e8 100644
> > --- a/config.c
> > +++ b/config.c
> > @@ -72,7 +72,7 @@ static char *parse_value(void)
> >                         }
> >                 }
> >                 if (space) {
> > -                       if (len)
> > +                       if (len && len < sizeof(value)-1)
> >                                 value[len++] = ' ';
> >                         space = 0;

Eh, or maybe better add a "continue;" here, so that only one char per
loop is read.

> >                 }

  reply	other threads:[~2009-04-08 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 22:13 [PATCH] Fix buffer overflow in config parser Thomas Jarosch
2009-04-08 22:58 ` Markus Heidelberg
2009-04-08 23:15   ` Markus Heidelberg [this message]
2009-04-09  7:59     ` Thomas Jarosch
2009-04-10 16:10       ` Markus Heidelberg

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=200904090115.17609.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --cc=git@vger.kernel.org \
    --cc=thomas.jarosch@intra2net.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.