Full Disclosure: Re: New Source Code Vulnerability Scanner (Free 30 Day Trial)

[netinfinity <netinfinity.securitylab () gmail com>]

I was thinking about another way to possible bypass this code.

POC:

grep -fruit

will trick the system into thinking it is a fruit thus crashing because of
stackoverflow and juice overflow.



On Sat, Dec 4, 2010 at 12:32 PM, Georgi Guninski <guninski () guninski com>wrote:

> On Fri, Dec 03, 2010 at 01:46:56AM -0800, Michal Zalewski wrote:
> > > grep -r ACIDBITCHES *
> > This code has two very obvious detection bypass vulnerabilities:
> >
> > 1) It fails to scan dotfiles in the starting directory,
> >
> > 2) It can be tricked into not producing any output by creating a file
> > named "-q" in the starting dir.
> >
> > Let me fire up my vulnerability research whitepaper generator.
> >
> > /mz
> implementation issues aside, are the theoretic foundations of the scanner
> correct?
>
> some points.
>
> 1. analyzing the grep(1) codebase. what if grep has anti-scanning backdoor
> - like a compiler backdoor?
>
> 2. the scanner reproducibly reports backdoors in /dev/urandom - it is
> even not an .EXE!
>
> --
> joro
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


-- 
www.google.com

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/