full-disclosure - RE: Unchecked buffer in mstask.dll

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: purdy at tecman.com (Curt Purdy)
Subject: RE: Unchecked buffer in mstask.dll

Nick FitzGerald wrote:
> > I'd say that's because you changed the filetype; pif files simply
> > contain information on how to handle a DOS executable; they aren't a
> > program themselves. All you did was make it get confused and kill
> > itself.
>
> Yeah, but how long is it now since we've been telling programmers
> "don't trust user-supplied data"??  (Hmmmm -- does it also fail on
> W2K3??)

No, in W2K3 you get "Cannot query the properties for this program. There may
not be enough memory available. blah blah" as opposed to 100% cpu in 2K.

Curt Purdy CISSP, GSEC, MCSE+I, CNE, CCDA
Information Security Engineer
DP Solutions

----------------------------------------

If you spend more on coffee than on IT security, you will be hacked.
What's more, you deserve to be hacked.
-- former White House cybersecurity adviser Richard Clarke