full-disclosure - Re: DLL hijacking with Autorun on a USB drive

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]

Message-ID: <1047938506-1282880018-cardhu_decombobulator_blackberry.rim.net-900909840-@bda124.bisx.prod.on.blackberry>
Date: Fri, 27 Aug 2010 03:33:38 +0000
From: "Sherwyn" <infolookup@...il.com>
To: paul.szabo@...ney.edu.au, full-disclosure-bounces@...ts.grok.org.uk,
	atul@...fence.com, Valdis.Kletnieks@...edu
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: DLL hijacking with Autorun on a USB drive

The reason I think you have to run wab.exe its because that's the foolish app that has the corresponding dll isssue. The cvs is just a bonus, I could be wrong.
Infolookup
http://infolookup.securegossip.com
www.twitter.com/infolookup

-----Original Message-----
From: paul.szabo@...ney.edu.au
Sender: full-disclosure-bounces@...ts.grok.org.uk
Date: Fri, 27 Aug 2010 13:07:54 
To: <atul@...fence.com>; <Valdis.Kletnieks@...edu>
Cc: <full-disclosure@...ts.grok.org.uk>
Subject: Re: [Full-disclosure] DLL hijacking with Autorun on a USB drive

Valdis.Kletnieks@...edu wrote:

>> Instead of it executing "wab.exe (Windows Address Book) and open the file
>> test.vcf", one can directly get any .exe file open.
>
> The whole point is that launching wab.exe and opening a test file is relatively
> innocuous - but if you can do that, you're basically holding the user's
> testicles in one hand and a very sharp knife in the other. It *could* have been
> anything - but we'll just do something mostly harmless just to be nice.

I thought that the point is that the victim does not invoke wab.exe
directly, but simply double-clicks on the innocent VCF file.

The attacker provides an innocent (and innocent-looking) VCF or similar
file, and places some DLLs in the same folder (or in some cases in a
lower-level folder). The unsafe application foolishly looks for its DLLs
in (or under) the current dir.

Cheers, Paul

Paul Szabo   psz@...hs.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of Sydney    Australia

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.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/