[Full-Disclosure] Re: new openssh exploit in the wild! * isFAKE AS SH@!*
adam at vattnet.net
Fri Sep 19 13:58:56 BST 2003
Probably a scriptkiddie or some random idiot. The fun part was
it came up totally different offsets then i mean TOTALLY different
each time you ran it and if you gave it a offset it would "work"
no matter what. For those people who ran it.. change all your
Vitaly Osipov wrote:
On Fri, 2003-09-19 at 14:21, V.O. wrote:
> Yeah, I missed the fact that after "calculating" the offset it starts to
> "exploit" in the same way as if it was given an offset as a parameter.
> Anyway, I simply wanted to note that whoever posted it here was either
> knowingly lying about its purpose or not having a clue about UNIX at all :)
> ----- Original Message -----
> From: "Adam Balogh" <adam at vattnet.net>
> To: "Full Disclosure" <full-disclosure at netsys.com>
> Sent: Friday, September 19, 2003 9:47 PM
> Subject: Re: [Full-Disclosure] Re: new openssh exploit in the wild! * isFAKE
> AS SH@!*
> > Vitaly Osipov wrote:
> > > which is obviously not true. Btw as far as I understand, the troyan code
> is triggered when
> > > the "exploit" is run with the offset specified, and not in a
> "bruteforcing" mode.
> > >
> > > W.
> > Me and my friend tried to run it on a lab-box thats not connected
> > directly to internet and doesnt relay mails. It doesn't use that
> > special offset as a trigger. We got so many "sys3" accounts in
> > /etc/passwd as many times we ran it plus those outgoing-mails que'd.
> > /Adam Balogh
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.netsys.com/full-disclosure-charter.html
Full-Disclosure is hosted and sponsored by Secunia.