public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 3/4] nscd: Avoid null pointer crashes after notfound response (bug 31678)
Date: Wed, 24 Apr 2024 12:39:38 -0400	[thread overview]
Message-ID: <16966637-8d8c-42d6-bdf3-baa5227284bb@gotplt.org> (raw)
In-Reply-To: <93eda86975719a1a40957e5f57fcb972b7daebbf.1713974801.git.fweimer@redhat.com>



On 2024-04-24 12:08, Florian Weimer wrote:
> The addgetnetgrentX call in addinnetgrX may have failed to produce
> a result, so the result variable in addinnetgrX can be NULL.
> Use db->negtimeout as the fallback value if there is no result data;
> the timeout is also overwritten below.
> 
> Also avoid sending a second not-found response.  (The client
> disconnects after receiving the first response, so the data stream did
> not go out of sync even without this fix.)  It is still beneficial to
> add the negative response to the mapping, so that the client can get
> it from there in the future, instead of going through the socket.
> ---

LGTM.

Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>

>   nscd/netgroupcache.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/nscd/netgroupcache.c b/nscd/netgroupcache.c
> index 8709fb77b6..8f9eb84e39 100644
> --- a/nscd/netgroupcache.c
> +++ b/nscd/netgroupcache.c
> @@ -509,14 +509,15 @@ addinnetgrX (struct database_dyn *db, int fd, request_header *req,
>   
>     datahead_init_pos (&dataset->head, sizeof (*dataset) + req->key_len,
>   		     sizeof (innetgroup_response_header),
> -		     he == NULL ? 0 : dh->nreloads + 1, result->head.ttl);
> +		     he == NULL ? 0 : dh->nreloads + 1,
> +		     result == NULL ? db->negtimeout : result->head.ttl);
>     /* Set the notfound status and timeout based on the result from
>        getnetgrent.  */
> -  dataset->head.notfound = result->head.notfound;
> +  dataset->head.notfound = result == NULL || result->head.notfound;
>     dataset->head.timeout = timeout;
>   
>     dataset->resp.version = NSCD_VERSION;
> -  dataset->resp.found = result->resp.found;
> +  dataset->resp.found = result != NULL && result->resp.found;
>     /* Until we find a matching entry the result is 0.  */
>     dataset->resp.result = 0;
>   
> @@ -564,7 +565,9 @@ addinnetgrX (struct database_dyn *db, int fd, request_header *req,
>         goto out;
>       }
>   
> -  if (he == NULL)
> +  /* addgetnetgrentX may have already sent a notfound response.  Do
> +     not send another one.  */
> +  if (he == NULL && dataset->resp.found)
>       {
>         /* We write the dataset before inserting it to the database
>   	 since while inserting this thread might block and so would

  reply	other threads:[~2024-04-24 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 16:08 [PATCH 0/4] Various nscd security fixes Florian Weimer
2024-04-24 16:08 ` [PATCH 1/4] nscd: Stack-based buffer overflow in netgroup cache (bug 31677) Florian Weimer
2024-04-24 16:27   ` Siddhesh Poyarekar
2024-04-24 16:08 ` [PATCH 2/4] nscd: Do not send missing not-found response in addgetnetgrentX (bug 31678) Florian Weimer
2024-04-24 16:35   ` Siddhesh Poyarekar
2024-04-24 16:08 ` [PATCH 3/4] nscd: Avoid null pointer crashes after notfound response " Florian Weimer
2024-04-24 16:39   ` Siddhesh Poyarekar [this message]
2024-04-24 16:08 ` [PATCH 4/4] nscd: netgroup: Use two buffers in addgetnetgrentX (bug 31680) Florian Weimer
2024-04-24 16:48   ` Siddhesh Poyarekar
2024-04-24 20:53 ` [PATCH 0/4] Various nscd security fixes Carlos O'Donell
2024-04-26  0:10 ` Cristian Rodríguez
2024-04-26  8:10   ` Florian Weimer

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=16966637-8d8c-42d6-bdf3-baa5227284bb@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).