Re: [PATCH] git-quiltimport: fix security risk because of un-sanitized $level.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] git-quiltimport: fix security risk because of un-sanitized $level.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:22

Pierre Habouzit [off-list ref] writes:
Signed-off-by: Pierre Habouzit <redacted>
---

  I assume that nobody will have a series with -p1000 in it :)
  sorry for this gross mistake in the first place.

  [ for the inattentive readers $level was used without quoting, for
    good reasons as it's sometime empty and then we don't want to pass
    an empty argument to git-apply, though someone could use that to run
    arbitrary commands, not nice ]
A traditional way to deal with that situation in shell scripts is to use
this idiom:

	${var_that_may_not_be_set+"$var_that_may_not_be_set"}

You can use :+ in place of + to also reject empty string on modern
systems.

#!/bin/sh
not_set=t ; unset not_set
is_set=t

report () {
	echo "I got $# args"
        i=1
        for it
        do
        	echo "$i: $it"
                i=$(( $i+1 ))
	done
        echo
}

report sending not_set ${not_set:+"$not_set"} string
report sending is_set ${is_set:+"$is_set"} string

Re: [PATCH] git-quiltimport: fix security risk because of un-sanitized $level.

From: Pierre Habouzit <hidden>
Date: 2016-06-15 22:44:22

On Wed, Mar 12, 2008 at 08:55:56PM +0000, Junio C Hamano wrote:
Pierre Habouzit [off-list ref] writes:
quoted
Signed-off-by: Pierre Habouzit <redacted>
---

  I assume that nobody will have a series with -p1000 in it :)
  sorry for this gross mistake in the first place.

  [ for the inattentive readers $level was used without quoting, for
    good reasons as it's sometime empty and then we don't want to pass
    an empty argument to git-apply, though someone could use that to run
    arbitrary commands, not nice ]
A traditional way to deal with that situation in shell scripts is to use
this idiom:

	${var_that_may_not_be_set+"$var_that_may_not_be_set"}
  Oh this is nicer than what I used indeed. My shell scripting skills
are quite limited :)

  Anyways, I happened to notice this stupid mistake when I re-read the
patch you merged. You probably want to use that trick instead (rather
than my poor sanitizing thing), and let git-apply sort out the rest.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help