public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: vvvvvv@google.com, elfutils-devel@sourceware.org
Cc: kernel-team@android.com, maennich@google.com
Subject: Re: [PATCH] libdw: check offset dwarf_formstring in all cases
Date: Fri, 17 Nov 2023 16:31:23 +0100	[thread overview]
Message-ID: <525de8c7fda5b1ebb41085c11d585f738f952e24.camel@klomp.org> (raw)
In-Reply-To: <20231116212922.4148717-1-vvvvvv@google.com>

Hi Aleksei,

On Thu, 2023-11-16 at 21:29 +0000, vvvvvv@google.com wrote:
> This check was initially added to test if offset overflows the safe
> prefix where any string will be null-terminated. However the check
> was placed in a wrong place and didn't cover all `attrp->form` cases.
> 
>     * libdw/dwarf_formstring.c (dwarf_formstring): Move offset check
>       right before returning the result.

Oops. I see how this happened for DW_FORM_strp and DW_FORM_line_strp we
use __libdw_read_offset which already check the section offset. But of
course those use d_size, not the string_section_size that was setup in
elf_begin_elf. So the check is also needed for them.

> Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
> ---
>  libdw/dwarf_formstring.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/libdw/dwarf_formstring.c b/libdw/dwarf_formstring.c
> index 0ee42411..65f03a5e 100644
> --- a/libdw/dwarf_formstring.c
> +++ b/libdw/dwarf_formstring.c
> @@ -173,11 +173,11 @@ dwarf_formstring (Dwarf_Attribute *attrp)
>  	off = read_4ubyte_unaligned (dbg, datap);
>        else
>  	off = read_8ubyte_unaligned (dbg, datap);
> -
> -      if (off >= data_size)
> -	goto invalid_offset;
>      }
>  
> +  if (off >= data_size)
> +    goto invalid_offset;
> +
>    return (const char *) data->d_buf + off;
>  }
>  INTDEF(dwarf_formstring)

Applied.

Thanks,

Mark

      reply	other threads:[~2023-11-17 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 21:29 vvvvvv
2023-11-17 15:31 ` Mark Wielaard [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=525de8c7fda5b1ebb41085c11d585f738f952e24.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=kernel-team@android.com \
    --cc=maennich@google.com \
    --cc=vvvvvv@google.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.
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).