From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: Jian J Wang <jian.j.wang@intel.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH] ShellPkg/UefiShellLevel3CommandsLib: fix string over-read
Date: Wed, 24 Jan 2018 11:35:36 +0800 [thread overview]
Message-ID: <8e457c40-fb85-5e9d-9dba-e3eff18cba4e@Intel.com> (raw)
In-Reply-To: <20180123021441.4784-1-jian.j.wang@intel.com>
On 1/23/2018 10:14 AM, Jian J Wang wrote:
> In the for-loop condition of original code, the expression
>
> *CurrentCommand != CHAR_NULL
>
> is put before expression
>
> CurrentCommand < SortedCommandList + SortedCommandListSize/sizeof(CHAR16)
>
> When CurrentCommand walks to the end of string buffer, one more character
> over the end of string buffer will be read and then stop.
>
> To fix this issue, just move the last expression to the first one. Because
> of short-circuit evaludation of and-expression, the following one
>
> *CurrentCommand != CHAR_NULL
>
> will not be evaluated if the expression before it is evaludated as FALSE.
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
> ---
> ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c b/ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c
> index a71ade3a20..75e3d74200 100644
> --- a/ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c
> +++ b/ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c
> @@ -397,7 +397,7 @@ ShellCommandRunHelp (
> CopyListOfCommandNamesWithDynamic(&SortedCommandList, &SortedCommandListSize);
>
> for (CurrentCommand = SortedCommandList
> - ; CurrentCommand != NULL && *CurrentCommand != CHAR_NULL && CurrentCommand < SortedCommandList + SortedCommandListSize/sizeof(CHAR16)
> + ; CurrentCommand < SortedCommandList + SortedCommandListSize/sizeof(CHAR16) && CurrentCommand != NULL && *CurrentCommand != CHAR_NULL
> ; CurrentCommand += StrLen(CurrentCommand) + 1
> ) {
> //
>
How about keep "CurrentCommand != NULL" in the beginning? I agree to
swap the other two checks.
--
Thanks,
Ray
next prev parent reply other threads:[~2018-01-24 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 2:14 [PATCH] ShellPkg/UefiShellLevel3CommandsLib: fix string over-read Jian J Wang
2018-01-24 3:35 ` Ni, Ruiyu [this message]
2018-01-24 3:40 ` Wang, Jian J
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 4:50 Jian J Wang
2018-01-24 5:47 ` Ni, Ruiyu
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-list 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=8e457c40-fb85-5e9d-9dba-e3eff18cba4e@Intel.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox