From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, kernel-janitors@vger.kernel.org,
samba-technical@lists.samba.org
Subject: Re: [patch] cifs: check offset in decode_ntlmssp_challenge()
Date: Tue, 31 Jan 2012 11:25:08 +0000 [thread overview]
Message-ID: <20120131112508.GE3294@mwanda> (raw)
In-Reply-To: <20120131054937.3e7ccf89@tlielax.poochiereds.net>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Tue, Jan 31, 2012 at 05:49:37AM -0500, Jeff Layton wrote:
> On Tue, 31 Jan 2012 11:52:01 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > We should check that we're not copying memory from beyond the end of the
> > blob.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> >
> > diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c
> > index d85efad..eb76741 100644
> > --- a/fs/cifs/sess.c
> > +++ b/fs/cifs/sess.c
> > @@ -395,6 +395,10 @@ static int decode_ntlmssp_challenge(char *bcc_ptr, int blob_len,
> > ses->ntlmssp->server_flags = le32_to_cpu(pblob->NegotiateFlags);
> > tioffset = le32_to_cpu(pblob->TargetInfoArray.BufferOffset);
> > tilen = le16_to_cpu(pblob->TargetInfoArray.Length);
> > + if (tioffset > blob_len || tioffset + tilen > blob_len) {
> > + cERROR(1, "tioffset + tilen too high %u + %u", tioffset, tilen);
> > + return -EINVAL;
> > + }
>
> Good catch.
>
> Do we really need a || here though? Would it not be sufficient to check
> if tioffset + tilen > blob_len? Or are you concerned about that value
> wrapping?
Yep. I was concerned about value wrapping.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, kernel-janitors@vger.kernel.org,
samba-technical@lists.samba.org
Subject: Re: [patch] cifs: check offset in decode_ntlmssp_challenge()
Date: Tue, 31 Jan 2012 14:25:08 +0300 [thread overview]
Message-ID: <20120131112508.GE3294@mwanda> (raw)
In-Reply-To: <20120131054937.3e7ccf89@tlielax.poochiereds.net>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Tue, Jan 31, 2012 at 05:49:37AM -0500, Jeff Layton wrote:
> On Tue, 31 Jan 2012 11:52:01 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > We should check that we're not copying memory from beyond the end of the
> > blob.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> >
> > diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c
> > index d85efad..eb76741 100644
> > --- a/fs/cifs/sess.c
> > +++ b/fs/cifs/sess.c
> > @@ -395,6 +395,10 @@ static int decode_ntlmssp_challenge(char *bcc_ptr, int blob_len,
> > ses->ntlmssp->server_flags = le32_to_cpu(pblob->NegotiateFlags);
> > tioffset = le32_to_cpu(pblob->TargetInfoArray.BufferOffset);
> > tilen = le16_to_cpu(pblob->TargetInfoArray.Length);
> > + if (tioffset > blob_len || tioffset + tilen > blob_len) {
> > + cERROR(1, "tioffset + tilen too high %u + %u", tioffset, tilen);
> > + return -EINVAL;
> > + }
>
> Good catch.
>
> Do we really need a || here though? Would it not be sufficient to check
> if tioffset + tilen > blob_len? Or are you concerned about that value
> wrapping?
Yep. I was concerned about value wrapping.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-31 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 8:52 [patch] cifs: check offset in decode_ntlmssp_challenge() Dan Carpenter
2012-01-31 8:52 ` Dan Carpenter
2012-01-31 10:49 ` Jeff Layton
2012-01-31 10:49 ` Jeff Layton
2012-01-31 11:25 ` Dan Carpenter [this message]
2012-01-31 11:25 ` Dan Carpenter
2012-01-31 11:50 ` Jeff Layton
2012-01-31 11:50 ` Jeff Layton
2012-01-31 13:42 ` Steve French
2012-01-31 13:43 ` Steve French
2012-01-31 13:43 ` Steve French
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=20120131112508.GE3294@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jlayton@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.