Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-08 Thread Dag-Erling Smørgrav
Konstantin Belousov writes: > Dag-Erling Smørgrav writes: > > Ah, I see. The port used sed to edit the file in-place instead of using > > a tool that understands Elf and would have adjusted the section length. > Really this cannot be done, as well as overriding the interpreter name > with the lo

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-08 Thread Konstantin Belousov
On Mon, Oct 08, 2018 at 12:04:29PM +0200, Dag-Erling Smørgrav wrote: > Konstantin Belousov writes: > > Dag-Erling Smørgrav writes: > > > The string isn't just unterminated, though. It's actually longer than > > > the section. To be precise, "/lib/ld-linux.so.2" is 18 characters long, > > > plus

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-08 Thread Dag-Erling Smørgrav
Konstantin Belousov writes: > Dag-Erling Smørgrav writes: > > The string isn't just unterminated, though. It's actually longer than > > the section. To be precise, "/lib/ld-linux.so.2" is 18 characters long, > > plus NUL makes 19. The section is supposed to be 17 bytes long. I > > don't mind

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-07 Thread Konstantin Belousov
On Mon, Oct 08, 2018 at 12:31:26AM +0200, Dag-Erling Smørgrav wrote: > Konstantin Belousov writes: > > writes: > >> Program Headers: > >> Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align > >> PHDR 0x34 0x08048034 0x08048034 0x00100 0x00100 R E 0x4 > >> I

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-07 Thread Dag-Erling Smørgrav
Konstantin Belousov writes: > writes: >> Program Headers: >> Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align >> PHDR 0x34 0x08048034 0x08048034 0x00100 0x00100 R E 0x4 >> INTERP 0x000134 0x08048134 0x08048134 0x00011 0x00011 R 0x1 >> [Re

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-06 Thread Konstantin Belousov
On Sat, Oct 06, 2018 at 09:46:36PM +0300, Konstantin Belousov wrote: > On Sat, Oct 06, 2018 at 09:21:04PM +0300, Konstantin Belousov wrote: > > On Sat, Oct 06, 2018 at 08:35:26PM +0300, l...@lena.kiev.ua wrote: > > > > Insufficient validation was performed in the ELF header parser, and > > > > mal

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-06 Thread Konstantin Belousov
On Sat, Oct 06, 2018 at 09:21:04PM +0300, Konstantin Belousov wrote: > On Sat, Oct 06, 2018 at 08:35:26PM +0300, l...@lena.kiev.ua wrote: > > > Insufficient validation was performed in the ELF header parser, and > > > malformed > > > or otherwise invalid ELF binaries were not rejected as they shou

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-06 Thread Konstantin Belousov
On Sat, Oct 06, 2018 at 08:35:26PM +0300, l...@lena.kiev.ua wrote: > > Insufficient validation was performed in the ELF header parser, and > > malformed > > or otherwise invalid ELF binaries were not rejected as they should be. > > What is invalid in the /usr/local/share/google-earth/googleearth-

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf

2018-10-06 Thread Lena
> Insufficient validation was performed in the ELF header parser, and malformed > or otherwise invalid ELF binaries were not rejected as they should be. What is invalid in the /usr/local/share/google-earth/googleearth-bin binary of the port google-earth-7.1.5.1557,3 ? FreeBSD 11.2-RELEASE-p4 Sep