mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexey Izbyshev <izbyshev@ispras.ru>
To: musl@lists.openwall.com
Cc: Alexey Kodanev <aleksei.kodanev@bell-sw.com>
Subject: Re: [musl] [PATCH] dns: check length field in tcp response message
Date: Thu, 29 Feb 2024 13:49:53 +0300	[thread overview]
Message-ID: <45da412c2c78a6d4c02023b172a778aa@ispras.ru> (raw)
In-Reply-To: <0c7a80b19cf470307d0cc9f2fe1b2d4e@ispras.ru>

On 2023-05-08 19:25, Alexey Izbyshev wrote:
> On 2023-03-22 16:16, Rich Felker wrote:
>> On Wed, Mar 22, 2023 at 03:29:16PM +0300, Alexey Kodanev wrote:
>>> The received length field in the message may be greater than the
>>> size of the 'answer' buffer in which the message resides. Currently,
>>> ABUF_SIZE is 768. And if we get a larger 'alen', it will result
>>> in an out-of-bounds reading during parsing, because 'alen' will
>>> be passed to __dns_parse() later:
>>> 
>>>     __dns_parse(abuf[i], alens[i], dns_parse_callback, &ctx);
>>> 
>>> To fix this, limit 'alen' to the size of the received buffer.
>>> ---
>>>  src/network/res_msend.c | 1 +
>>>  1 file changed, 1 insertion(+)
>>> 
>>> diff --git a/src/network/res_msend.c b/src/network/res_msend.c
>>> index fef7e3a2..291853de 100644
>>> --- a/src/network/res_msend.c
>>> +++ b/src/network/res_msend.c
>>> @@ -297,6 +297,7 @@ int __res_msend_rc(int nqueries, const unsigned 
>>> char *const *queries,
>>>  			int rcode = answers[i][3] & 15;
>>>  			if (rcode != 0 && rcode != 3)
>>>  				goto out;
>>> +			if (alen > asize) alen = asize;
>>> 
>>>  			/* Storing the length here commits the accepted answer.
>>>  			 * Immediately close TCP socket so as not to consume
>>> --
>>> 2.25.1
>> 
>> This is incorrect. It breaks res_send, whose contract is to return the
>> full answer length even if it did not fit, so that the caller can
>> retry with the appropriate size.
>> 
>> Instead, name_from_dns just needs to clamp the value before passing it
>> to __dns_parse.
>> 
> Not only name_from_dns, but also getnameinfo. The patch is attached.
> 
Pinging due to the approaching release. Did the patch fall through 
cracks?

Thanks,
Alexey

  reply	other threads:[~2024-02-29 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 12:29 Alexey Kodanev
2023-03-22 13:16 ` Rich Felker
2023-03-22 13:48   ` Alexey Kodanev
2023-03-22 14:07     ` Rich Felker
2023-05-08 16:25   ` Alexey Izbyshev
2024-02-29 10:49     ` Alexey Izbyshev [this message]
2024-02-29 15:36       ` Rich Felker

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=45da412c2c78a6d4c02023b172a778aa@ispras.ru \
    --to=izbyshev@ispras.ru \
    --cc=aleksei.kodanev@bell-sw.com \
    --cc=musl@lists.openwall.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://git.vuxu.org/mirror/musl/

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).