From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/4] json-streamer: Don't crash when input exceeds nesting limit
Date: Thu, 29 Oct 2015 10:25:49 -0600 [thread overview]
Message-ID: <5632488D.8040109@redhat.com> (raw)
In-Reply-To: <1446122683-2355-3-git-send-email-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]
On 10/29/2015 06:44 AM, Markus Armbruster wrote:
> We limit nesting depth and input size to defend against input
> triggering excessive heap or stack memory use (commit 29c75dd
> json-streamer: limit the maximum recursion depth and maximum token
> count). However, when the nesting limit is exceeded,
> parser_context_peek_token()'s assertion fails.
>
> Broken in commit 65c0f1e "json-parser: don't replicate tokens at each
> level of recursion".
>
> To reproduce stuff 1025 open braces or brackets into QMP.
>
> Fix by taking the error exit instead of the normal one.
>
> Reported-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qobject/json-streamer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
However, a couple comments about the context:
> if (type == JSON_ERROR) {
> goto out_emit_bad;
> } else if (parser->brace_count < 0 ||
> parser->bracket_count < 0 ||
> (parser->brace_count == 0 &&
> parser->bracket_count == 0)) {
> goto out_emit;
Should we go to out_emit_bad for brace_count/bracket_count < 0, and save
out_emit only for the case where brace == bracket == 0? Can we even
trigger negative counts (probably by attempting unpaired "{]]", but will
that trigger earlier errors?)
> } else if (parser->token_size > MAX_TOKEN_SIZE ||
> parser->bracket_count > MAX_NESTING ||
> parser->brace_count > MAX_NESTING) {
> /* Security consideration, we limit total memory allocated per
object
> * and the maximum recursion depth that a message can force.
> */
> goto out_emit;
> }
>
> return;
>
>out_emit_bad:
> /* clear out token list and tell the parser to emit and error
Typo: s/and error/an error/
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-10-29 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 12:44 [Qemu-devel] [PATCH 0/4] json-streamer: Fix up code to limit nesting and size Markus Armbruster
2015-10-29 12:44 ` [Qemu-devel] [PATCH 1/4] json-streamer: Apply nesting limit more sanely Markus Armbruster
2015-10-29 16:22 ` Eric Blake
2015-10-29 12:44 ` [Qemu-devel] [PATCH 2/4] json-streamer: Don't crash when input exceeds nesting limit Markus Armbruster
2015-10-29 16:25 ` Eric Blake [this message]
2015-11-23 17:21 ` Markus Armbruster
2015-10-29 12:44 ` [Qemu-devel] [PATCH 3/4] check-qjson: Add test for JSON nesting depth limit Markus Armbruster
2015-10-29 16:36 ` Eric Blake
2015-10-29 18:33 ` Markus Armbruster
2015-10-29 12:44 ` [Qemu-devel] [PATCH 4/4] json-streamer: Limit number of tokens in addition to total size Markus Armbruster
2015-10-29 16:43 ` Eric Blake
2015-10-29 18:27 ` Markus Armbruster
2015-10-29 23:35 ` Eric Blake
2015-10-30 7:52 ` Markus Armbruster
2015-10-30 15:22 ` Eric Blake
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=5632488D.8040109@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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).