Full Disclosure mailing list archives

Re: Major gcc 4.1.1 and up security issue

From: "Roflek of TK53" <roflek1337 () gmail com>
Date: Tue, 16 Jan 2007 08:46:56 +0100

On 1/16/07, Resident_Geek <resident_geek () phreaker net> wrote:

That's an integer overflow. It's well known. See Phrack Volume 0x0b,
Issue 0x3c, Phile 0x0a for an introduction to this basic issue.


Felix' point was that the latest gcc breaks code that is supposed to
_detect_ integer overflows.

Cheers, Roflek

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Current thread:

Major gcc 4.1.1 and up security issue Felix von Leitner (Jan 15)
- Re: Major gcc 4.1.1 and up security issue Resident_Geek (Jan 15)
  - Re: Major gcc 4.1.1 and up security issue Roflek of TK53 (Jan 15)
- Re: Major gcc 4.1.1 and up security issue Valdis . Kletnieks (Jan 16)
  - Re: Major gcc 4.1.1 and up security issue Marcus Graf (Jan 17)
    - Re: Major gcc 4.1.1 and up security issue Valdis . Kletnieks (Jan 17)
- Re: Major gcc 4.1.1 and up security issue Pavel Kankovsky (Jan 20)
  - Re: Major gcc 4.1.1 and up security issue Marcin Owsiany (Jan 21)
    - Re: Major gcc 4.1.1 and up security issue Valdis . Kletnieks (Jan 22)
    - Re: Major gcc 4.1.1 and up security issue Marcin Owsiany (Jan 22)
    - Re: Major gcc 4.1.1 and up security issue Valdis . Kletnieks (Jan 22)
  - Message not available
    - Re: Major gcc 4.1.1 and up security issue Michele Cicciotti (Jan 21)
- <Possible follow-ups>
- Re: Major gcc 4.1.1 and up security issue Gwiasda Patrick (Jan 16)

(Thread continues...)