I would suggest chapter 23 (Security) from the Camel book (Programming Perl 3rd ed).
The first thing you can do, as long as you don't need anything from the shell (i.e. globbing), is to use system in a list context. Something like:
@args = qw/-p $project->name/; push @args, '-f' if $force; system "inc_seqs", @args;
This prevents potentially bad metacharacters from being interpreted by the shell (which system would use otherwise). In addition, to help out with taint checking, the following sub is suggested to test for tainted variables:
sub is_tainted { my $arg = shift; my $nada = substr( $arg, 0, 0 ); # zero-length local $@; # preserve caller's version eval { eval "# $nada" }; return length($@) != 0; }
Good luck!

In reply to Re: cgi taint trouble by abatkin
in thread cgi taint trouble by sabkat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.