public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] tcp: Explicitly check option length field values in tcp_opt_get()
Date: Thu, 5 Jan 2023 15:34:19 +1100	[thread overview]
Message-ID: <Y7ZTS14nly34g/cD@yekko> (raw)
In-Reply-To: <20230104174421.633847-1-sbrivio@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

On Wed, Jan 04, 2023 at 06:44:21PM +0100, Stefano Brivio wrote:
> Reported by Coverity (CWE-606, Untrusted loop bound), and actually
> harmless because we'll exit the option-scanning loop if the remaining
> length is not enough for a new option, instead of reading past the
> header.
> 
> In any case, it looks like a good idea to explicitly check for
> reasonable values of option lengths.
> 
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
>  tcp.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/tcp.c b/tcp.c
> index 26037b3..1e0a338 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -1117,6 +1117,10 @@ static int tcp_opt_get(const char *opts, size_t len, uint8_t type_find,
>  			break;
>  		default:
>  			type = *(opts++);
> +
> +			if (*(uint8_t *)opts < 2 || *(uint8_t *)opts > len)
> +				return -1;
> +
>  			optlen = *(opts++) - 2;
>  			len -= 2;
>  

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-01-05  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 17:44 [PATCH] tcp: Explicitly check option length field values in tcp_opt_get() Stefano Brivio
2023-01-05  4:34 ` David Gibson [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=Y7ZTS14nly34g/cD@yekko \
    --to=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).