From: Kai Tietz <ktietz70@googlemail.com>
To: Binutils <binutils@sourceware.org>
Cc: Nick Clifton <nickc@redhat.com>
Subject: [patch bfd]: Prevent possible buffer overflow on pdata-section sorting
Date: Wed, 06 Apr 2011 16:50:00 -0000 [thread overview]
Message-ID: <BANLkTimv7dy1SPBi=dKP+fnWayX13VpU7g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hello,
this issue was reported by H. Becker to me. He found that the code in
peXXigen.c about pdata-section sorting might cause a buffer-overrun
for large pdata-data. By working in private allocated buffer -
instead of using the pfinfo->contents - avoids this.
ChangeLog
2011-04-06 Kai Tietz
* peXXigen.c (_bfd_XXi_final_link_postscripte): Sort pdata in temporary
buffer.
Tested for x86_64-w64-mingw32. Ok for apply?
Regards,
Kai
[-- Attachment #2: pdata_x64_sort.txt --]
[-- Type: text/plain, Size: 1074 bytes --]
Index: src/bfd/peXXigen.c
===================================================================
--- src.orig/bfd/peXXigen.c 2010-12-21 19:33:07.000000000 +0100
+++ src/bfd/peXXigen.c 2011-04-06 18:19:45.945394800 +0200
@@ -2459,14 +2459,22 @@ _bfd_XXi_final_link_postscript (bfd * ab
if (sec)
{
bfd_size_type x = sec->rawsize ? sec->rawsize : sec->size;
+ bfd_byte *tmp_data = NULL;
- if (x && bfd_get_section_contents (abfd, sec, pfinfo->contents, 0, x))
+ if (x)
+ tmp_data = bfd_malloc (x);
+
+ if (tmp_data != NULL)
{
- qsort (pfinfo->contents,
- (size_t) ((sec->size <x ? sec->size : x) / 12),
- 12, sort_x64_pdata);
- bfd_set_section_contents (pfinfo->output_bfd, sec,
- pfinfo->contents, 0, x);
+ if (bfd_get_section_contents (abfd, sec, tmp_data, 0, x))
+ {
+ qsort (tmp_data,
+ (size_t) ((sec->size <x ? sec->size : x) / 12),
+ 12, sort_x64_pdata);
+ bfd_set_section_contents (pfinfo->output_bfd, sec,
+ tmp_data, 0, x);
+ }
+ free (tmp_data);
}
}
}
next reply other threads:[~2011-04-06 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 16:50 Kai Tietz [this message]
2011-04-06 21:55 ` h.becker
2011-04-07 1:09 ` Alan Modra
2011-04-07 5:55 ` Kai Tietz
2011-04-07 6:15 ` Kai Tietz
2011-04-07 8:52 ` Alan Modra
2011-04-07 14:31 ` Kai Tietz
2011-04-09 4:40 ` Alan Modra
2011-04-09 9:50 ` Kai Tietz
[not found] ` <20110409131155.GH19002@bubble.grove.modra.org>
[not found] ` <BANLkTikediRDiabar9P0k526O4Pyy_qWSQ@mail.gmail.com>
[not found] ` <20110409140103.GI19002@bubble.grove.modra.org>
2011-04-09 16:07 ` Kai Tietz
2011-04-11 4:08 ` rawsize and output sections Alan Modra
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='BANLkTimv7dy1SPBi=dKP+fnWayX13VpU7g@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=binutils@sourceware.org \
--cc=nickc@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.
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).