full-disclosure - shell:windows command question

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: <40ED4C3B.3050806@sdf.lonestar.org>
From: bkfsec at sdf.lonestar.org (Barry Fitzgerald)
Subject: shell:windows command question

Andreas Sandblad wrote:

>Did some quick search on Bugzilla and came up with the following:
>
>Mozilla allows external protocols as discussed in:
>http://bugzilla.mozilla.org/show_bug.cgi?id=167475
>They seem to blacklist the following external protocol handlers:
>(patch http://bugzilla.mozilla.org/attachment.cgi?id=102263&action=view)
>hcp, vbscript, javascript, ms-help, vnd.ms.radio
>
>A simple solution would be to add the shell protocol to this list.
>Personally I think a secure blacklist is hard to maintain as new
>dangerous external protocols could be invented by third-parties leaving
>Mozilla vulnerable again.
>
>  
>

Completely agreed.

There should be a whitelist, not a blacklist... a safe protocols list.

             -Barry