From: Julia Lawall <julia.lawall@lip6.fr>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
arve@android.com, riandrews@android.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] staging: android: Replace strcpy with strlcpy
Date: Sat, 11 Mar 2017 22:34:48 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703112231280.2270@hadrien> (raw)
In-Reply-To: <CALrZqyPw8rU8RuoAT83rxjVGdckvuS7F1gqVXDcerQ0kXEM30g@mail.gmail.com>
On Sun, 12 Mar 2017, SIMRAN SINGHAL wrote:
> On Sun, Mar 12, 2017 at 2:53 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> >
> > On Sun, 12 Mar 2017, simran singhal wrote:
> >
> >> Replace strcpy with strlcpy as strcpy does not check for buffer
> >> overflow.
> >> This is found using Flawfinder.
> >>
> >> Signed-off-by: simran singhal <singhalsimran0@gmail.com>
> >> ---
> >>
> >> v2:
> >> -Correcting the place of the parenthesis
> >>
> >> drivers/staging/android/ashmem.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
> >> index 7cbad0d..eb2f4ef 100644
> >> --- a/drivers/staging/android/ashmem.c
> >> +++ b/drivers/staging/android/ashmem.c
> >> @@ -548,7 +548,8 @@ static int set_name(struct ashmem_area *asma, void __user *name)
> >> if (unlikely(asma->file))
> >> ret = -EINVAL;
> >> else
> >> - strcpy(asma->name + ASHMEM_NAME_PREFIX_LEN, local_name);
> >> + strlcpy(asma->name + ASHMEM_NAME_PREFIX_LEN, local_name,
> >> + sizeof(asma->name + ASHMEM_NAME_PREFIX_LEN));
> >
> > This appears to be the old patch.
> >
> > Actually, looking closer, I don't think this is right at all. There seems
> > to be a goal of leaving some space at the beginning of asma->name. So the
> > amount of space available for local_name would be computed using a
> > subtraction, not an addition.
> >
> Julia, By mistake I sent the wrong patch.
> And I am not getting you want to mention which space.
The following is the whole asma->name array. The | in the middle is the
offset ASHMEM_NAME_PREFIX_LEN. The xxx characters are in the
ASHMEM_NAME_PREFIX_LEN region. The space for local_name is only the part
indicates with the ys. This space is smaller than the size of asma->name.
In your calculation, you are allowing it to be larger. You will
potentially overflow the buffer by 2 * ASHMEM_NAME_PREFIX_LEN.
--------------------------
|xxxxxxx|yyyyyyyyyyyyyyyyyy|
--------------------------
julia
prev parent reply other threads:[~2017-03-11 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 21:17 simran singhal
2017-03-11 21:23 ` [Outreachy kernel] " Julia Lawall
2017-03-11 21:30 ` SIMRAN SINGHAL
2017-03-11 21:34 ` Julia Lawall [this message]
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=alpine.DEB.2.20.1703112231280.2270@hadrien \
--to=julia.lawall@lip6.fr \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=riandrews@android.com \
--cc=singhalsimran0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®