refspec.c: use rhs in parse_refspec instead of potentially uninitialized item->dst
PATCH 5/5 refspec.c: use rhs in parse_refspec instead of potentially uninitialized item->dst
'item->dst' has not been assigned if '!rhs' is true. As the caller is allowed to pass in uninitialized memory (we don't assume 'item' was zeroed out before calling), this fixes an access to uninitialized memory.
---
applies on bw/refspec-api
refspec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
refspec.c +1 -1
@@ -108,7 +108,7 @@ static int parse_refspec(struct refspec_item *item, const char *refspec, int fet* - empty is not allowed. * - otherwise it must be a valid looking ref. */ -if (!item->dst) { +if (!rhs) {if (check_refname_format (item->src, flags))return 0 ; }else if (!*item->dst) {
Signature · 1 line
2.17.0.582.gccdcbd54c44.dirty
Quoted 3 lines · Stefan Beller
'
item->dst' has not been assigned if '!rhs' is true. As the caller is allowed to pass in uninitialized memory (we don't assume 'item' was zeroed out before calling), this fixes an access to uninitialized memory.
Did I miss the other 4 patches that this might depend on it?
refspec.c static int parse_refspec(struct refspec_item *item, const char *refspec, int fet · line 114
Quoted 13 lines
refspec.c +1
-1@@ -108,7 +108,7 @@ static int parse_refspec(struct refspec_item *item, const char *refspec, int fet* - empty is not allowed. * - otherwise it must be a valid looking ref. */ -if (!item->dst) { +if (!rhs) {if (check_refname_format (item->src, flags))return 0 ; }else if (!*item->dst) {
Perhaps a better fisx is to explicitly assign NULL to item->dst when we see there is no right-hand-side.
Aside from the "uninitialized" issue, the original if/else cascade around here makes a lot more sense than the updated version. If we do not leave item->dst uninitialized, the control (and the readers' understanding) can flow without having to carry the invariant "item->dst is set ONLY when rhs != NULL" throughout this codepath, in order to understand that this if/else cascade is asking: is pointer NULL? then do one thing, otherwise is pointee NUL? then do another thing, otherwise we have a non-empty string so do something on it.
Quoted 2 lines · Junio C Hamano
Perhaps a better fisx is to explicitly assign NULL to
item->dstwhen we see there is no right-hand-side.
-- >8 --
Subject: [PATCH] refspec-api: avoid uninitialized field in refspec item
When parse_refspec() function was created at 3eec3700 ("refspec:
factor out parsing a single refspec", 2018-05-16) to take a caller supplied piece of memory to fill parsed refspec_item, it forgot that a refspec without colon must set item->dst to NULL to let the users of refspec know that the result of the fetch does not get stored in an ref on our side.
---
* The original before that change filled a callee prepared piece of memory that was obtained from xcalloc(), and did not need to explicitly assign NULL to the field after noticing that there is no colon in the refspec, so it is understandable how this misconvesion happened.
refspec.c | 2 ++ 1 file changed, 2 insertions(+)
refspec.c +2 -0
@@ -48,6 +48,8 @@ static int parse_refspec(struct refspec_item *item, const char *refspec, int fetsize_t rlen =strlen (++rhs); is_glob = (1 <= rlen &&strchr (rhs,'*' )); item->dst =xstrndup (rhs, rlen); + }else { + item->dst =NULL ; } llen = (rhs ? (rhs - lhs -1 ) :strlen (lhs));
Signature · 1 line
2.18.0-rc0
Quoted 8 lines · Junio C Hamano
Quoted 2 lines · Junio C Hamano
Perhaps a better fisx is to explicitly assign NULL to
item->dstwhen we see there is no right-hand-side.-- >8 --
Subject: [PATCH] refspec-api: avoid uninitialized field in refspec item
Quoted 8 lines
When
parse_refspec()function was created at3eec3700("refspec:
factor out parsing a single refspec", 2018-05-16) to take a caller supplied piece of memory to fill parsedrefspec_item, it forgot that a refspec without colon must setitem->dstto NULL to let the users of refspec know that the result of the fetch does not get stored in an ref on our side.Signed-off-by Junio C Hamano <[email protected]>
This looks correct. Thanks for writing the patch.
Quoted 1 line
Did I miss the other 4 patches that this might depend on it?
No. I was sloppy and developed a couple of patches on top
of pu and then tried to put them onto their respective branches. and then I forgot to correct the patch counts after figuring out the right branch to apply this to.
Thanks,
Stefan