Although it doesn't apply to this worm really, even if BIND is not run as root, it usually starts that way, so if you could exploit this hole, you could plant a "bomb" that would effectively root the box the next time BIND was run as root (such as a restart), which could then be provoked with any number of DoS attacks...

But not running BIND as root is certainly the first step. What we need is a clean-slate, audited-code DNS implementation that is configuration-file compatible with BIND -- That would certainly make migration easier for the rest of the world, and maybe we'd get away from these BIND-related nasties for good.

Signature void where prohibited by law.

In reply to Re: Re: WORM: Warning to all LINUX/PERL monks by Clownburner
in thread WORM: Warning to all LINUX/PERL monks by scottstef

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.