TheNotorious
Im dying slowly.
- Oct 4, 2014
- 228
- 41
A lot of peoples made retro with Xampp.
There are some Vulnerabilities contains Xampp.
I just wanna let you know.
Okay, its fine if ur cms is non exploitable, or u fixed the exploits like xss, etc..
Xampp 1.8.2 - SQL Exploit
There are some Vulnerabilities contains Xampp.
I just wanna let you know.
Okay, its fine if ur cms is non exploitable, or u fixed the exploits like xss, etc..
Xampp 1.8.2 - SQL Exploit
You must be registered for see links
ANDsleep(3)&interpret=1&titel=555-666-0606
Xampp 1.7.7 - 'PHP_SELF' Variable Scripting Vulnerabilities
An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and launch other attacks.
These issues affect XAMPP 1.7.7 for Windows.
These issues affect XAMPP 1.7.7 for Windows.
You must be registered for see links
"><script>alert(1)</script>
You must be registered for see links
"><script>alert(1)</script>
You must be registered for see links
"><script>alert(1)</script>Xampp 1.7.4 - Cross-site Scripting.
XAMPP is prone to multiple cross-site scripting vulnerabilities because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.
These issues affect XAMPP 1.7.4 for Windows and prior.
An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.
These issues affect XAMPP 1.7.4 for Windows and prior.
You must be registered for see links
You must be registered for see links
And Xampp 1.7.2 got exploit called:
Change (root) user password.
At the older versions of xampp "xamppsecurity.php" was allowed
only for localhost but at version 1.7.2 i accessible by all
And you can change the .htacces user & pass and the phpMyAdmin pass
only for localhost but at version 1.7.2 i accessible by all
You must be registered for see links
And you can change the .htacces user & pass and the phpMyAdmin pass
Xampp 1.7.3
File disclosure
XAMPP is vulnerable to a remote file disclosure attack.
The vulnerability exists within the web application supplied with XAMPP.
showcode.php:
<?php
echo '<br><br>';
if ($_REQUEST['showcode'] != 1) {
echo '<a href="'.$_SERVER['PHP_SELF'].'?showcode=1">'.$TEXT['global-showcode'].'</a>';
} else {
$file = file_get_contents(basename($_SERVER['PHP_SELF']));
echo "<h2>".$TEXT['global-sourcecode']."</h2>";
echo "<textarea cols='100' rows='10'>";
echo htmlspecialchars($file);
echo "</textarea>";
}
?>
showcode.php relies on basename($_SERVER['PHP_SELF']) to retrieve the path.
What $_SERVER['PHP_SELF'] actually does is retrieve is the path of the requested file.
basename() parses the last element of that path using "/" as a delimiter.
Traveling through the directory tree, though, requires the "/" character that is used by basename() as a delimiter.
Therefor directory traveling it is not achieved but it is possible to view file contents from any drive, and the XAMPP htdocs directory.
Cross Site Scripting (1.7.3)
It is interesting to see the same programming error lead to another security vulnerability.
Some PHP scripts in the XAMPP dir rely on $_SERVER['PHP_SELF'] for retrieving the "action" tag for HTML forms.
This can be exploited to perform Cross Site Scripting attacks.
biorhythm.php (line 75):
<form method="post" action="<?php echo basename($_SERVER['PHP_SELF']); ?>">
dork: "inurl:xampp/biorhythm.php"
XAMPP is vulnerable to a remote file disclosure attack.
The vulnerability exists within the web application supplied with XAMPP.
You must be registered for see links
showcode.php:
<?php
echo '<br><br>';
if ($_REQUEST['showcode'] != 1) {
echo '<a href="'.$_SERVER['PHP_SELF'].'?showcode=1">'.$TEXT['global-showcode'].'</a>';
} else {
$file = file_get_contents(basename($_SERVER['PHP_SELF']));
echo "<h2>".$TEXT['global-sourcecode']."</h2>";
echo "<textarea cols='100' rows='10'>";
echo htmlspecialchars($file);
echo "</textarea>";
}
?>
showcode.php relies on basename($_SERVER['PHP_SELF']) to retrieve the path.
What $_SERVER['PHP_SELF'] actually does is retrieve is the path of the requested file.
basename() parses the last element of that path using "/" as a delimiter.
Traveling through the directory tree, though, requires the "/" character that is used by basename() as a delimiter.
Therefor directory traveling it is not achieved but it is possible to view file contents from any drive, and the XAMPP htdocs directory.
Cross Site Scripting (1.7.3)
You must be registered for see links
"><script>alert("XSS")</script>
You must be registered for see links
"><script>alert("XSS")</script>It is interesting to see the same programming error lead to another security vulnerability.
Some PHP scripts in the XAMPP dir rely on $_SERVER['PHP_SELF'] for retrieving the "action" tag for HTML forms.
This can be exploited to perform Cross Site Scripting attacks.
biorhythm.php (line 75):
<form method="post" action="<?php echo basename($_SERVER['PHP_SELF']); ?>">
dork: "inurl:xampp/biorhythm.php"
At the least, use IIS.
- DanielBlur