I'm neither smarter, nor more awake than anyone here :) but I'll throw in a couple of ideas for you:

First of all as kutsu mentioned reworking any code to fail properly and thereby probably nullify any attempt to exploit the vulnerability is the easy way to go, and as you mention, since you're willing to do it, go for it. It should not be that hard if you don't have too many files to go through.

If you look at the docs a little more in depth you'll see that not all vendors released an upgrade of Perl for this, or acknowledged it as a serious hole. Second you'll see it's a local only exploit (not remotely exploitable) so assess the risk on a system by system basis - e.g. there'll be much less risk on an application server with few if any local users. Third by the time you see any vulnerability on SecurityFocus or Regis and Kathy Lee, it's been around for ages in the wild..

It seems that in this particular case it's more important to clean up code and lock down filesystem access, and monitor your systems for unusal patterns and unauth access, along with a per-system code and user assessment, than rushing out to upgrade Perl everywhere..

In reply to Re: security patch for perl 5.6.1 by hsinclai
in thread security patch for perl 5.6.1 by Qiang

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.