full-disclosure - Re: URI handling woes in Acrobat Reader, Netscape, Miranda, Skype

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: <83DB8BFB2FBE455BAA870A310F23BDDA@control3>
Date: Sun, 7 Oct 2007 23:03:03 -0400
From: "Geo." <geoincidents@....net>
To: <full-disclosure@...ts.grok.org.uk>,
	<bugtraq@...urityfocus.com>
Subject: Re: URI handling woes in Acrobat Reader, Netscape,
	Miranda, Skype

----- Original Message ----- 
From: "Glynn Clements" <glynn@...ements.plus.com>

> URIs which it passes to an external handler (e.g. mailto:), it only
> needs to identify the scheme (to select the correct handler); it is
> the handler's responsibility to validate its own URIs (i.e. mail
> programs need to validate mailto: URIs).

I don't agree. Whatever program takes input from an untrusted source, it's 
that programs duty to sanitize the input before passing it on to internal 
components. It's like a firewall, you filter before it gets inside the 
system.

Example, an ftp server has to sanitize filenames to prevent useage of 
streams on NTFS, you don't blame the filesystem that the input gets passed 
to, it's the job of the ftp server to do the sanitizing of untrusted input.

Geo. 

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/