Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Vuln-Dev
[Top] [All Lists]

Re: PHP Event Calendar 1.5.1 (index.php) Remote File Include Vulnerabili

Subject: Re: PHP Event Calendar 1.5.1 (index.php) Remote File Include Vulnerability
Date: Wed, 29 Nov 2006 16:43:01 -0500
Systems that install 1.5.1 (fresh install rather than upgrade) should not be vulnerable.

"philip anselmo" wrote:

Vulnerable Code:
***************
include $path_to_calendar."calendar.php";


Looking at the few lines prior to that:

  extract($HTTP_GET_VARS);
  if(!@include './data/global.php'){
          echo "Can't open ./data/global.php";
          exit;
  }

  extract($PATHS);
  include $path_to_calendar."calendar.php";


After successfully running 'install.php', the 'data/global.php' file will contain something like this:

  $PATHS=array(
  "path_to_calendar" => "/[blah]/cl_files/",
  "path_to_calendar_img" => "/[blah]/cl_files/img/",
  "WEB_path_to_calendar_img" => "http://[site]/[blah]/cl_files/img/";,
  "path_to_data" => "/[blah]/cl_files/data/"
  );


The include statement will use "/[blah]/cl_files/" instead of the user-supplied parameter in $HTTP_GET_VARS.


And, indeed, testing confirms that the static parameter is used and that
the reported exploit URL does not work.

Systems that have been upgraded from an earlier version in an improper
manner may be a different story.

Stuart



<Prev in Thread] Current Thread [Next in Thread>