linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] lib: Add range check for SDP_SVC_ATTR_RSP/SDP_SVC_SEARCH_ATTR_RSP
Date: Tue, 09 Jul 2013 21:24:25 +0200	[thread overview]
Message-ID: <105649341.YkdKDHxtUP@athlon> (raw)
In-Reply-To: <1372278395-22582-1-git-send-email-szymon.janc@gmail.com>

On Wednesday 26 June 2013 22:26:35 Szymon Janc wrote:
> This is an improved version of recently reverted commit 1796f00e8465.
> Response size is verified against minimal allowed value only if it is
> complete response. If response is partial it is allowed by spec that
> it will be split in arbitrary manner.
> 
> Verified against Nokia BH217 on which original commit caused
> regression.
> ---
>  lib/sdp.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/lib/sdp.c b/lib/sdp.c
> index d8bfc51..54a99b6 100644
> --- a/lib/sdp.c
> +++ b/lib/sdp.c
> @@ -4243,6 +4243,14 @@ int sdp_process(sdp_session_t *session)
>  		rsp_count = bt_get_be16(pdata);
>  		SDPDBG("Attrlist byte count : %d", rsp_count);
> 
> +		/* Valid range for rsp_count is 0x0002-0xFFFF */
> +		if (t->rsp_concat_buf.data_size == 0 && rsp_count < 0x0002) {
> +			t->err = EPROTO;
> +			SDPERR("Protocol error: invalid AttrList size");
> +			status = SDP_INVALID_PDU_SIZE;
> +			goto end;
> +		}
> +
>  		/*
>  		 * Number of bytes in the AttributeLists parameter(without
>  		 * continuation state) + AttributeListsByteCount field size.

ping

  reply	other threads:[~2013-07-09 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 20:26 [PATCH] lib: Add range check for SDP_SVC_ATTR_RSP/SDP_SVC_SEARCH_ATTR_RSP Szymon Janc
2013-07-09 19:24 ` Szymon Janc [this message]
2013-07-10  9:37   ` Johan Hedberg

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=105649341.YkdKDHxtUP@athlon \
    --to=szymon.janc@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).