public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Long Qin <qin.long@intel.com>, edk2-devel@lists.01.org
Cc: ting.ye@intel.com
Subject: Re: [PATCH] CryptoPkg/BaseCryptLib: Fix potential integer overflow issue.
Date: Wed, 24 Oct 2018 18:59:21 +0200	[thread overview]
Message-ID: <9f9769c6-8c3e-73d0-1a0c-06d81de27704@redhat.com> (raw)
In-Reply-To: <20181024132202.10596-1-qin.long@intel.com>

On 10/24/18 15:22, Long Qin wrote:
> The LookupFreeMemRegion() in RuntimeMemAllocate.c is used to look-up
> free memory region for runtime resource allocation, which was designed
> to support runtime authenticated variable service.
> The direct offset subtractions in this function may bring possible
> integer overflow issue.
> 
> This patch is to add the extra parameter checks to remove this possible
> overflow risk.
> 
> Cc: Ye Ting <ting.ye@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Long Qin <qin.long@intel.com>
> ---
>  .../Library/BaseCryptLib/SysCall/RuntimeMemAllocation.c    | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/CryptoPkg/Library/BaseCryptLib/SysCall/RuntimeMemAllocation.c b/CryptoPkg/Library/BaseCryptLib/SysCall/RuntimeMemAllocation.c
> index 463f2bf855..92bb9ddccd 100644
> --- a/CryptoPkg/Library/BaseCryptLib/SysCall/RuntimeMemAllocation.c
> +++ b/CryptoPkg/Library/BaseCryptLib/SysCall/RuntimeMemAllocation.c
> @@ -2,7 +2,7 @@
>    Light-weight Memory Management Routines for OpenSSL-based Crypto
>    Library at Runtime Phase.
>  
> -Copyright (c) 2009 - 2017, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2009 - 2018, Intel Corporation. All rights reserved.<BR>
>  This program and the accompanying materials
>  are licensed and made available under the terms and conditions of the BSD License
>  which accompanies this distribution.  The full text of the license may be found at
> @@ -141,6 +141,12 @@ LookupFreeMemRegion (
>  
>    StartPageIndex = RT_SIZE_TO_PAGES (mRTPageTable->LastEmptyPageOffset);
>    ReqPages       = RT_SIZE_TO_PAGES (AllocationSize);
> +  if (ReqPages > mRTPageTable->PageCount) {
> +    //
> +    // No enough region for object allocation.
> +    //
> +    return (UINTN)(-1);
> +  }
>  
>    //
>    // Look up the free memory region with in current memory map table.
> @@ -176,6 +182,12 @@ LookupFreeMemRegion (
>    // Look up the free memory region from the beginning of the memory table
>    // until the StartCursorOffset
>    //
> +  if (ReqPages > StartPageIndex) {
> +    //
> +    // No enough region for object allocation.
> +    //
> +    return (UINTN)(-1);
> +  }
>    for (Index = 0; Index < (StartPageIndex - ReqPages); ) {
>      //
>      // Check Consecutive ReqPages Pages.
> 

As far as I can see, "RuntimeCryptLib.inf" (where this file is used) is
only linked into runtime DXE modules -- not SMM modules. That means this
issue is not a security bug, because runtime DXE modules can be
overwritten by the OS anyway. (They reside in normal RAM.) Can you
please confirm?

Nonetheless, it would be nice to explain in the commit message, what
exactly "ReqPages" depends on.

If needed, please file a BZ as well. (I'm not saying it's required, but
you might want to consider it, and reference it in the commit message.)

Thanks
Laszlo


  reply	other threads:[~2018-10-24 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 13:22 [PATCH] CryptoPkg/BaseCryptLib: Fix potential integer overflow issue Long Qin
2018-10-24 16:59 ` Laszlo Ersek [this message]
2018-10-25 13:23   ` Long, Qin
2018-10-26  0:50 ` Ye, Ting

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=9f9769c6-8c3e-73d0-1a0c-06d81de27704@redhat.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