From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 4/4] input: Validate SDP HIDDescriptorList subattributes
Date: Mon, 7 Jan 2013 10:27:34 +0200 [thread overview]
Message-ID: <20130107082734.GA8075@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1357501558-3457-4-git-send-email-anderson.lizardo@openbossa.org>
Hi Lizardo,
On Sun, Jan 06, 2013, Anderson Lizardo wrote:
> It should not be assumed that remote SDP attributes are in a compliant
> format. This fixes a couple of invalid pointer access on invalid data.
> ---
> profiles/input/device.c | 60 ++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 46 insertions(+), 14 deletions(-)
I've applied the first three patches, but this one needs a bit of fixing
up:
> + if (d->dtd < SDP_SEQ8 || d->dtd > SDP_SEQ32)
> + goto invalid_desc;
Please always be explicit on what values you're checking for instead of
assuming that the reader of the code knows what's contained within some
range. In this case there's already a convenient SDP_IS_SEQ() macro you
could use.
> + if (d->dtd < SDP_SEQ8 || d->dtd > SDP_SEQ32)
> + goto invalid_desc;
Same here.
> + if (!d || d->dtd < SDP_TEXT_STR8 || d->dtd > SDP_TEXT_STR32)
> + goto invalid_desc;
I suppose the best way to handle this one is to add a SDP_IS_STR() macro
(in a separate patch) to lib/sdp.h and then use it in this patch.
Johan
next prev parent reply other threads:[~2013-01-07 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 19:45 [PATCH BlueZ 1/4] input: Change extract_hid_record() return type Anderson Lizardo
2013-01-06 19:45 ` [PATCH BlueZ 2/4] input: Move HID device name creation to separate function Anderson Lizardo
2013-01-06 19:45 ` [PATCH BlueZ 3/4] input: Use SDP library functions for reading attributes Anderson Lizardo
2013-01-06 19:45 ` [PATCH BlueZ 4/4] input: Validate SDP HIDDescriptorList subattributes Anderson Lizardo
2013-01-07 8:27 ` Johan Hedberg [this message]
2013-01-07 11:59 ` Anderson Lizardo
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=20130107082734.GA8075@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--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).