[UNIX] Multiple WHM AutoPilot Vulnerabilities

From: SecuriTeam (support_at_securiteam.com)
Date: 12/29/04

  • Next message: SecuriTeam: "[UNIX] kpdf Buffer Overflow Vulnerability"
    To: list@securiteam.com
    Date: 29 Dec 2004 14:42:35 +0200

    The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
    - - promotion

    The SecuriTeam alerts list - Free, Accurate, Independent.

    Get your security news from a reliable source.

    - - - - - - - - -

      Multiple WHM AutoPilot Vulnerabilities


    "Started by a webhost looking for more out of a simple management script,
    Brandee Diggs (Owner of Spinn A Web Cafe, Founder of Benchmark Designs)
    setout to build an internal management system that could handle the day to
    day operations of a normal hosting company. The key was to remove the need
    to constantly watch your orders and manage the installs. Alas,
    <http://www.whmautopilot.com/> WHM AutoPilot was born".

    Multiple security vulnerabilities have been discovered in WHM AutoPilot
    ranging from Cross Site Scripting to PHP Code Injection.


    Cross Site Scripting:
    There are a significant number of cross site scripting issues in WHM
    AutoPilot. Most of these are caused by calling scripts directly and
    specifying certain variable values yourself. Below are a few examples,
    though there are many more XSS holes than just the examples am showing


    We believe that every file in the /themes/blue/ directory can be
    manipulated in this way, and of course this can be used to steal a users
    credentials or render hostile code.

    File Inclusion Vulnerability:
    WHM AutoPilot is susceptible to several potentially very dangerous file
    include vulnerabilities. Below are several examples of how files can be
    included and possibly executed remotely.


    This can be used to include php scripts and possibly take control of the
    webserver and more. A user does not have to be logged in to exploit this
    vulnerability either so that just makes it even more dangerous.

    Notice in the first sample, the "header.php/step_one.php"? Well, that was
    done to get around a piece of code that looked something like what is
    pasted just below.

    if (ereg("test.php", $PHP_SELF)==true)
        include $server_inc."/step_one_tables.php";

    Which works because $PHP_SELF will return the value of
    "header.php/step_one.php" expectedly. The below excerpt was taken from the
    PHP manual.

    The filename of the currently executing script, relative to the document
    root. For instance, $_SERVER['PHP_SELF'] in a script at the address
    http://example.com/test.php/foo.bar would be /test.php/foo.bar. The
    __FILE__ constant contains the full path and filename of the current (i.e.
    included) file."

    Information Disclosure:
    By default WHM AutoPilot is shipped with a phpinfo() script that is
    accessible to anyone. As far as I know WHM AutoPilot needs register
    globals to work, but if you want to check php settings anyway the file can
    be found in the root directory as "phpinfo.php".


    The information has been provided by <mailto:security@gulftech.org>
    GulfTech Security.
    The original article can be found at:


    This bulletin is sent to members of the SecuriTeam mailing list.
    To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com
    In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com


    The information in this bulletin is provided "AS IS" without warranty of any kind.
    In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.

  • Next message: SecuriTeam: "[UNIX] kpdf Buffer Overflow Vulnerability"