phc-discussions - Re: [PHC] Some Schvrch issues

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87d2gzoz5c.fsf@wolfjaw.dfranke.us>
Date: Wed, 02 Apr 2014 23:44:15 -0400
From: Daniel Franke <dfoxfranke@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Some Schvrch issues

Some further issues:

Lines 86 and 87 are buffer overflows if inlen + saltlen > 2048. Line 114
is a buffer overflow if outlen > 2048. There are no checks for these
conditions.

When t_cost = m_cost = 0 and outlen = 2048, the only irreversible
operation performed is discarding the final value of 'carry' in the
stir() function. This makes Schvrch vulnerable to a straightforward 2^64
preimage attack when these settings are used.