full-disclosure - openssh remote exploit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: avalon at caligula.anu.edu.au (Darren Reed)
Subject: openssh remote exploit

In some mail from auto64746@...hmail.com, sie said:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Look closer.
> 
> buffer->alloc += len + 32768;
>    if (buffer->alloc > 0xa00000)
>    fatal("buffer_append_space: alloc %u not supported",buffer->alloc);
> 
> buffer->buf = xrealloc(buffer->buf, buffer->alloc);
> goto restart;
> 
> i do not have belief of giving the codepath but we must take buffer_free
> and make overflow by '\0'.
> this is not exploit of 2.4.x as malloc never return null. unless malloc
> w00d00.

Ah, I see what you mean.  I was looking at the code assuming all the
functions called worked perfectly and that fatal() did nothing fancy.
In reading it through, I took an attitude of not looking at any other
files or functions to see what they did as the pointer didn't mention
those and who knows where it might have ended or how much time it would
have taken ?  Remember, this is OpenSSH - the world's most perfect
software.

And  I'm sure this will manage to be another remote exploit that
the OpenBSD team will find a way to not count on their front page.

Cheers,
Darren