full-disclosure - Re: New Source Code Vulnerability Scanner (Free 30 Day Trial)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <553356.10154.qm@web121404.mail.ne1.yahoo.com>
Date: Sat, 4 Dec 2010 10:07:58 -0800 (PST)
From: Adam Kration <adamkration@...il.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: New Source Code Vulnerability Scanner (Free
	30 Day Trial)

Don't forget you can add a pipe to filter the pulp.

grep -fruit | grep -v pulp

-v will omit pulp, and various regexes and additives can fortify with calcium or vitamin C.

--- On Sat, 12/4/10, netinfinity <netinfinity.securitylab@...il.com> wrote:

From: netinfinity <netinfinity.securitylab@...il.com>
Subject: Re: [Full-disclosure] New Source Code Vulnerability Scanner (Free 30 Day Trial)
To: full-disclosure@...ts.grok.org.uk
Date: Saturday, December 4, 2010, 11:53 AM

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@...inski.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

-----Inline Attachment Follows-----

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

Content of type "text/html" skipped

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