full-disclosure - Can CERT VU#786920 be right?

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: <200707181125.l6IBPIjQ007304@asti.maths.usyd.edu.au>
Date: Wed, 18 Jul 2007 21:25:18 +1000
From: Paul Szabo <psz@...hs.usyd.edu.au>
To: full-disclosure@...ts.grok.org.uk
Subject: Can CERT VU#786920 be right?

I sent the following to CERT (a few hours ago, no reply yet):

> In http://www.kb.cert.org/vuls/id/786920 you wrote:
>
>   Disabling the AIM protocol handler will mitigate this vulnerability.
>   To unregister the protocol handlers, delete or rename the following
>   registry keys:
>   HKEY_CLASSES_ROOT\AOL
>
> I believe that renaming that key does NOT unregister the handler.
> Windows looks for registry values of "URL Protocol" (almost?) anywhere
> within the registry, not just (directly) under HKCR. And anyway, how
> would renaming AOL to XYZ affect the AIM handler...

Now I wonder if they can in fact be right... please enlighten me.

Cheers,

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/