BugTraq
Re: DJB's students release 44 *nix software vulnerability advisories Dec 20 2004 11:14PM
Jonathan T Rockway (jrockw2 uic edu) (7 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:22PM
laffer1 (laffer1 mail foolishgames com) (1 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 22 2004 06:06AM
Jonathan Rockway (jrockw2 uic edu)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:11PM
Thor (thor hammerofgod com)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:50PM
Dave Holland (dh3 sanger ac uk) (1 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:55PM
sean (infamous41md hotpop com)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:34PM
milw0rm Inc. (milw0rm gmail com) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 11:58PM
Jack Lloyd (lloyd randombit net)
Re: DJB's students release 44 *nix software vulnerabilityadvisories Dec 21 2004 09:30PM
Antoine Martin (antoine nagafix co uk) (1 replies)
On Tue, 2004-12-21 at 14:34 -0600, milw0rm Inc. wrote:
> /*
> Two points.
> Regarding local versus remote, look at it this way: You have a 100%
> secure system. Then you install NASM. Now a user FROM THE NETWORK can
> send you some tainted assembly code for you to assemble and he can
> compromise your account.
> */
>
> quote "for you to assemble"
>
> Its a user error. Your not remotely exploiting anything but the trust
> from the user.
Although I agree with you that in the vast majority of cases this
exploit would require user interaction, there are corner cases where
this can be successfully exploited remotely:
* gentoo systems by compromising one of the master servers (or more
simply by hijacking the connection to one of the those servers) to serve
the malicious file - but in this case you probably don't really need
this exploit to compromise the system.
* other automated build systems (no generic name comes to mind) which
download the files they work on from other systems - which may not be
trusted to the point that grants a shell but just enough to provide
input.
* compromising any open-source software's repository that already uses
nasm and placing the exploit file in the default build target - tough,
but not impossible (it has happened before and will happen again).

I guess this is just not "remotely expoitable" in the usual sense
(direct attack vector)

A.M
>
> //str0ke
>

[ reply ]
Re: DJB's students release 44 *nix software vulnerabilityadvisories Dec 22 2004 12:23PM
Chris Paget (ivegotta tombom co uk)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:22PM
Stephen Harris (bugtraq spuddy org)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:14PM
Raymond M. Reskusich (reskusic uiuc edu)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 07:59PM
David F. Skoll (dfs roaringpenguin com) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 22 2004 03:50AM
Jonathan Rockway (jrockw2 uic edu) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 23 2004 04:49PM
Michal Zalewski (lcamtuf dione ids pl)


 

Privacy Statement
Copyright 2010, SecurityFocus