full-disclosure - BMP WMPlayer vulnerability

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

Message-ID: <001401c632ab$3f82a200$c801a8c0@Nemo>
Date: Thu Feb 16 09:33:16 2006
From: karma at designfolks.com.au (Karma)
Subject: BMP WMPlayer vulnerability

Anyone determined the offset where the heap alloc routine is located ? I diffed the two wmp.dll's and they are significantly changed, I think the code is very much optimised in this release, many routines are changed. I have been tracing the mallocs and GlobalAllocs without any luck. Hoping someone is having better luck than I.

Basically, it would be great to know if 0 is the only size that causes the error and how the error is handled. 

Where is the size field located in the BMP metadata ? 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060216/c47981ad/attachment.html