Joey if you could allocate a CVE ID I'll handle an upload
for Etch.
Steve
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Steve Kemp wrote:
Joey if you could allocate a CVE ID I'll handle an upload
for Etch.
Please use CVE-2007-2833.
Regards,
Joey
--
Still can't talk about what I can't talk about. Sorry. -- Bruce Schneier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
* Moritz Muehlenhoff:
glibc 2.3.4 introduced more secure heap management, which renders several
code injection attacks moot.
I think these additional checks have already been bypassed. Shall I
dig up a reference?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Steve Langasek [EMAIL PROTECTED] writes:
So if there's no evidence of arbitrary code execution, I think
it's appropriate here to downgrade the bug -- but the security
team should also be apprised.
Fine with me.
--
,''`.
: :' :Romain Francoise [EMAIL PROTECTED]
`. `'
On Sun, Feb 04, 2007 at 01:12:21PM +0100, Romain Francoise wrote:
reassign 408929 emacs21
tags 408929 patch
quit
This is a known bug in the way Emacs computes the size of some GIF
images; the attached patch (adapted from a similar change in CVS)
fixes the crash for me.
Ok, thanks for the
reassign 408929 emacs21
tags 408929 patch
quit
This is a known bug in the way Emacs computes the size of some GIF
images; the attached patch (adapted from a similar change in CVS)
fixes the crash for me.
Thanks,
--
,''`.
: :' :Romain Francoise [EMAIL PROTECTED]
`. `'
Steve Langasek [EMAIL PROTECTED] writes:
I've tagged this bug security, because it wasn't clear to me
whether this was a potentially exploitable problem. Do you think
that tag applies here?
Yes, I think it does. Crashing Emacs is a denial of service attack
against the various applications
severity 408929 important
thanks
On Sun, Feb 04, 2007 at 01:56:40PM +0100, Jérôme Marant wrote:
I'll ask that we tag this bug as etch-ignore: there are tons of bugs like
this one in Emacs and there are multiple chances to expose such bugs
by using many different packages.
Futhermore, emacs21
Steve Langasek wrote:
So if there's no evidence of arbitrary code execution, I think it's
appropriate here to downgrade the bug -- but the security team should also
be apprised.
glibc 2.3.4 introduced more secure heap management, which renders several
code injection attacks moot. (most notably
Package: emacs21
Version: 21.4a+1-3
Severity: critical
The spam email appended below causes emacs to crash with
*** glibc detected *** free(): invalid next size (normal): 0x08706488 ***
Fatal error (6).
or even simply with
Fatal error (11).Segmentation fault
To reproduce:
start
10 matches
Mail list logo
