Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Why use taint

by simon.proctor (Vicar)
on Mar 09, 2002 at 22:22 UTC ( #150625=note: print w/replies, xml ) Need Help??

in reply to Re: Re: Errors in my (simple?) CGI Script!
in thread Errors in my (simple?) CGI Script!

Well for a start its coming from the outside world. In my opinion all CGI programs should be able to run under taint mode before they get put onto a live server. All incoming data must be taint checked before being used. In this case we expect a string so we can strip everything that isn't and so remove all the nasty shell characters and \00.

In the context of the program above it might appear overkill but arguably its better to get into good habits early.

Replies are listed 'Best First'.
Re: Why use taint
by theguvnor (Chaplain) on Mar 10, 2002 at 01:19 UTC

    I'm not sure why you are asserting that all parameters must specifically be untainted. I would tend to agree with Juerd that unless you're using it in a system call, it doesn't pose a security problem. (theguvnor would welcome any enlightenment to the contrary).

    On the other hand, I don't understand Juerd's assertion that Perl's tainting is such a problem.

    1. You don't have to run -T if you don't want.
    2. Even when you use it, you only have to untaint those variables that you want to use in system calls.

    So I don't know why Juerd is so down on Perl's tainting mechanism...


      I think in fairness I was neither asserting or insisting someone use taint. Rather I was expressing that it could be used and voicing a personal opinion that it should. If it wasn't clear enough that it was a matter of opinion only then apologies for any confusion caused.

    A reply falls below the community's threshold of quality. You may see it by logging in.
Re: Why use taint
by Juerd (Abbot) on Mar 09, 2002 at 22:36 UTC

    All incoming data must be taint checked before being used.

    I disagree.

    Only data that is used in external calls must be taint checked. For example, when a name is put in a cookie, just for fun, there's absolutely no reason to taint check it (you should think about encoding it, though).

    I dislike Perl's tainting, because it lets _all_ external input be tainted (and that decreases performance), while some things are never used in a dangerous environment. While it might be a good idea for beginners to always taint everything, I personally HATE -T, and would rather be able to have a lexical taint pragma, and taint and untaint functions for those moments where you want to have a check on some data, or when you know some data is completely safe.


      While not as absolute as a taint pragma, the Taint module offers the ability to introduce taint checkpoints in your code. For example:

      use Taint; warn "Oops" if tainted $num, @ids; kill $num, @ids;

      While not as encompassing as a taint pragma, these checkpoints, if placed correctly can tighten up your code without invoking the entire script with the -T. The use of this module however does require some forethought and understanding of tainted data and identification of vunerable execution points within your code.


      perl -e 's&&[@.]/&&s&.com.&_&&&print'

      Only data that is used in external calls must be taint checked. For example, when a name is put in a cookie, just for fun, there's absolutely no reason to taint check it
      Absolutely no reason to taint check? What if the name they give you contains "\r\n"? If you blindly copied that name into a Set-Cookie header, someone could insert arbitrary HTTP headers and HTML content into your output with a cross-site scripting attack.
      you should think about encoding it, though
      Encoding will solve this problem in most cases. automatically url-escapes cookie contents, which is yet another reason to always use it.

        As you said, encoding solves the problem. And I don't like, and won't use it unless forced. Not even for cookies, I'd use CGI::Cookie for that, if I have to (note: CGI::Cookies is used by Or I'd just write a quick-and-dirty regex like s/(\W)/sprintf "%%%02x", ord $1/ge.


Re: Why use taint
by shotgunefx (Parson) on Mar 10, 2002 at 01:44 UTC
    Personally I don't use taint. Whenever I do anything that could touch the outside I treat it like a bomb. (With great care.) But for someone less familiar with the dangers, It can't hurt. Though it might not help either unless they understand why they are doing and what is dangerous.


    "To be civilized is to deny one's nature."

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://150625]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (2)
As of 2022-08-09 19:48 GMT
Find Nodes?
    Voting Booth?

    No recent polls found