Jonathan Rockway discovered a buffer overflow in nasm, the general-purpose x86 assembler, which could lead to the execution of arbitrary code when compiling a maliciously crafted assembler source file. See: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1287 https://bugzilla.redhat.com/beta/show_bug.cgi?id=143081 https://bugzilla.redhat.com/beta/show_bug.cgi?id=143080 http://www.debian.org/security/2005/dsa-623 ------- Bug moved to this database by dkl 2005-03-30 18:31 ------- This bug previously known as bug 2429 at https://bugzilla.fedora.us/ https://bugzilla.fedora.us/show_bug.cgi?id=2429 Originally filed under the Fedora Legacy product and Package request component. Unknown priority P2. Setting to default priority "normal". Unknown platform PC. Setting to default platform "All". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Um, maybe it's just me, but: what were you going to do with that potentially-malicious code once it *was* assembled? I mean, in the (only slightly!) bigger picture, how does this help? I'm just sayin'.
The problem is that a crafted asm file can be used to execute an arbitrary code *while* compiling the source. I discovered yet another buffer vsprintf overflow even in the latest 0.98.39 release. I'll attach here a patch to fix CAN-2004-1287 and this newly found overflow. These patches may need to be backported to the older nasm versions.
Created attachment 113220 [details] Patch to fix CAN-2004-1287 and the additional buffer overflow in outieee.c
Yeah, I understand the problem; I just think it's kind of funny because, y'know, if you have untrusted ASM code and you assemble it, *then* what are you going to do with it? Anyway, thanks very much for your help with these.
Not a problem, this was rather funny also for me as I'd never imagine that I can kill my machine by compiling asm source ;)
Fedora Legacy project has ended. These will not be fixed by Fedora Legacy.