From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: buffer overflow in _bfd_XX_print_ce_compressed_pdata
Date: Wed, 26 Oct 2022 17:57:23 +1030 [thread overview]
Message-ID: <Y1jhW48kuVC8Ig2d@squeak.grove.modra.org> (raw)
More fuzzed fun.
* peXXigen.c (_bfd_XX_print_ce_compressed_pdata): Use smaller of
virt_size and bfd section size as limit of function table.
diff --git a/bfd/peXXigen.c b/bfd/peXXigen.c
index c5a7f7bf7ac..0232a63d558 100644
--- a/bfd/peXXigen.c
+++ b/bfd/peXXigen.c
@@ -2026,6 +2026,8 @@ _bfd_XX_print_ce_compressed_pdata (bfd * abfd, void * vfile)
}
start = 0;
+ if (stop > datasize)
+ stop = datasize;
for (i = start; i < stop; i += onaline)
{
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2022-10-26 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y1jhW48kuVC8Ig2d@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@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).