This won't work if the perl code on the back end works like this:
my $string = "a_sample_string"; my $re = q[(?{ tr|_| | })(.*)]; # or my $re = some CGI parameter extraction $string =~ m/$re/; print $1;
Which is, you must admit much more likely than forming a string and passing it to eval (but some people do some amazingly unsecure things). Of course, if they pass it through the qr operator, we're back in business. (I assume they aren't using the obviously insecure use re 'eval';)

The lesson here for anyone writing CGI scripts that do regexp manipulation is this:
Using qr allows regexps to execute arbitrary code. DO NOT take arbitrary user input and feed it to qr unless you mean to allow arbitrary code execution.

-- @/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/; map{y/X_/\n /;print}map{pop@$_}@/for@/

In reply to Re^4: a small regexp question by fizbin
in thread a small regexp question by newroz

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.