Point and Shoot Report
Site report for plesk
Scanned on October 10 2010
Reported on October 10 2010
SAMPLE
Site Name |
Start Time |
End Time |
Total Time |
Status |
---|---|---|---|---|
plesk |
October 10, 2010 11:49, EDT |
October 10, 2010 12:25, EDT |
36 minutes |
Success |
The audit was performed on one system which was found to be active and was scanned.
![]() |
There were 29 vulnerabilities found during this scan. Of these, 6 were critical vulnerabilities. Critical vulnerabilities require immediate attention. They are relatively easy for attackers to exploit and may provide them with full control of the affected systems. 18 vulnerabilities were severe. Severe vulnerabilities are often harder to exploit and may not provide the same access to affected systems. There were 5 moderate vulnerabilities discovered. These often provide information to attackers that may assist them in mounting subsequent attacks on your network. These should also be fixed in a timely manner, but are not as urgent as the other vulnerabilities.
![]() |
![]() |
There were 209 occurrences of the http-basic-auth-cleartext vulnerability, making it the most common vulnerability. There were 255 vulnerabilities in the Web category, making it the most common vulnerability category.
![]() |
The mysql-yassl-multiple-bof, mysql-myisam-table-privilege-check-bypass and mysql-yassl-certdecodergetname-multiple-bofs vulnerabilities pose the highest risk to the organization with a risk score of 90. Vulnerability risk scores are calculated by looking at the likelihood of attack and impact, based upon CVSS metrics. The impact and likelihood are then multiplied by the number of instances of the vulnerability to come up with the final risk score.
One operating system was identified during this scan.
There were 9 services found to be running during this scan.
![]() |
![]() |
The DNS, DNS-TCP, FTP, HTTP, HTTPS, IMAP, Microsoft Remote Display Protocol, MySQL and POP services were found on 1 systems, making them the most common services. The HTTP service was found to have the most vulnerabilities during this scan with 228 vulnerabilities.
Node |
Operating System |
Risk |
Aliases |
---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
Microsoft Windows Server 2008 R2 |
7.41 |
|
The HTTP Basic Authentication scheme is not considered to be a secure method of user authentication (unless used in conjunction with some external secure system such as TLS/SSL), as the user name and password are passed over the network as cleartext.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/ADw-script AD4-alert(42) ADw-/ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/ADw-script AD4-alert(42) ADw-/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/ADw-script AD4-alert(42) ADw-/script AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/php/ADw-script AD4-alert(42) ADw-/script AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/Entries ( http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/Entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/Root ( http://vulnerable.plesk.smb.10.2.0.host/test/php/CVS/Root ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/DEADJOE ( http://vulnerable.plesk.smb.10.2.0.host/test/php/DEADJOE ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.CGI ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.CGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.FCGI ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.FCGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php. ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php. ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.old ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php~ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.php~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP3 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP3 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP4 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP4 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP5 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHP5 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PL ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PL ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PY ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.PY ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.RB ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.RB ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.SH ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.SH ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/test.SHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/php/test.SHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/Trace.axd ( http://vulnerable.plesk.smb.10.2.0.host/test/php/Trace.axd ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/WS_FTP.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/php/WS_FTP.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/python/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/%23adojavas.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/python/%23adojavas.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/%23adovbs.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/python/%23adovbs.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/python/%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/%3f.jsp%5C ( http://vulnerable.plesk.smb.10.2.0.host/test/python/%3f.jsp%5C ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/.svn/ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/.svn/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/.svn/entries ( http://vulnerable.plesk.smb.10.2.0.host/test/python/.svn/entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adojavas.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/adovbs.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/ADw-script AD4-alert(42) ADw-/ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/ADw-script AD4-alert(42) ADw-/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/ADw-script AD4-alert(42) ADw-/script AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/python/ADw-script AD4-alert(42) ADw-/script AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/ ( http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/Entries ( http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/Entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/Root ( http://vulnerable.plesk.smb.10.2.0.host/test/python/CVS/Root ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/DEADJOE ( http://vulnerable.plesk.smb.10.2.0.host/test/python/DEADJOE ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.CGI ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.CGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.FCGI ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.FCGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP3 ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP3 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP4 ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP4 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP5 ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHP5 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PL ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PL ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.py ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.py ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PY ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.PY ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.py. ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.py. ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.RB ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.RB ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.SH ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.SH ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/test.SHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/python/test.SHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/Trace.axd ( http://vulnerable.plesk.smb.10.2.0.host/test/python/Trace.axd ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/python/WS_FTP.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/python/WS_FTP.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/Trace.axd ( http://vulnerable.plesk.smb.10.2.0.host/test/Trace.axd ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/WS_FTP.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/WS_FTP.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/ ( http://vulnerable.plesk.smb.10.2.0.host/test/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/.svn/entries ( http://vulnerable.plesk.smb.10.2.0.host/test/.svn/entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/adojavas.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/adojavas.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/adovbs.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/adovbs.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/ADw-script AD4-alert(42) ADw-/script AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/ADw-script AD4-alert(42) ADw-/script AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23adojavas.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23adojavas.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23adovbs.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23adovbs.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23test.aspx%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%23test.aspx%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%3f.jsp%5C ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/%3f.jsp%5C ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/.svn/ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/.svn/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/.svn/entries ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/.svn/entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adojavas.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/adovbs.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ADw-script AD4-alert(42) ADw-/ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ADw-script AD4-alert(42) ADw-/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ADw-script AD4-alert(42) ADw-/script AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/ADw-script AD4-alert(42) ADw-/script AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/Entries ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/Entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/Root ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/CVS/Root ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/DEADJOE ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/DEADJOE ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx%3f.jsp%5C ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx%3f.jsp%5C ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.old ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx~ ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/test.aspx~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/Trace.axd ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/Trace.axd ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/WS_FTP.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/aspnet/WS_FTP.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/CVS/Entries ( http://vulnerable.plesk.smb.10.2.0.host/test/CVS/Entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/CVS/Root ( http://vulnerable.plesk.smb.10.2.0.host/test/CVS/Root ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/DEADJOE ( http://vulnerable.plesk.smb.10.2.0.host/test/DEADJOE ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23adojavas.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23adojavas.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23adovbs.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23adovbs.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23info2www.cgi%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23info2www.cgi%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23info2www.pl%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23info2www.pl%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23test.pl%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%23test.pl%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/%3f.jsp%5C ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/%3f.jsp%5C ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/.svn/ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/.svn/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/.svn/entries ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/.svn/entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adojavas.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/adovbs.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/ADw-script AD4-alert(42) ADw-/ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/ADw-script AD4-alert(42) ADw-/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/ADw-script AD4-alert(42) ADw-/script AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/ADw-script AD4-alert(42) ADw-/script AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/Entries ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/Entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/Root ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/CVS/Root ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/DEADJOE ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/DEADJOE ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.CGI ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.CGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi. ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi. ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.old ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi~ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.cgi~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.FCGI ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.FCGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP3 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP3 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP4 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP4 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP5 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHP5 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PL ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PL ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl. ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl. ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.html ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.html ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.old ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.tdy ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.tdy ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl~ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.pl~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PY ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.PY ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.RB ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.RB ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.SH ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.SH ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.SHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/info2www.SHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.CGI ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.CGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.FCGI ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.FCGI ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP3 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP3 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP4 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP4 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP5 ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHP5 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PL ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PL ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl. ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl. ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.html ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.html ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.old ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.tdy ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.tdy ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl~ ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.pl~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PY ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.PY ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.RB ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.RB ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.SH ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.SH ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.SHTML ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/test.SHTML ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/Trace.axd ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/Trace.axd ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/perl/WS_FTP.LOG ( http://vulnerable.plesk.smb.10.2.0.host/test/perl/WS_FTP.LOG ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ( http://vulnerable.plesk.smb.10.2.0.host/test/php/?P=+ADw-script+AD4-alert(42)+ADw-/script+AD4- ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/%23adojavas.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/%23adojavas.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/%23adovbs.inc%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/%23adovbs.inc%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/%23test.php%23 ( http://vulnerable.plesk.smb.10.2.0.host/test/php/%23test.php%23 ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/%3f.jsp ( http://vulnerable.plesk.smb.10.2.0.host/test/php/%3f.jsp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/%3f.jsp%5C ( http://vulnerable.plesk.smb.10.2.0.host/test/php/%3f.jsp%5C ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/.svn/ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/.svn/ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/.svn/entries ( http://vulnerable.plesk.smb.10.2.0.host/test/php/.svn/entries ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.bak ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.old ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.old ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.tmp ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc.tmp ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc~ ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adojavas.inc~ ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc ) 1: |
vulnerable.plesk.smb.10.2.0.host:80 |
Running vulnerable HTTP service.
http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.bak ( http://vulnerable.plesk.smb.10.2.0.host/test/php/adovbs.inc.bak ) 1: |
Source |
Reference |
---|---|
URL |
http://tools.ietf.org/html/rfc2617 ( http://tools.ietf.org/html/rfc2617 ) |
Use Basic Authentication over TLS/SSL (HTTPS)
Enable HTTPS on the Web server. The TLS/SSL protocol will protect cleartext Basic Authentication credentials.
Use Digest Authentication
Replace Basic Authentication with the alternative Digest Authentication scheme. By modern cryptographic standards Digest Authentication is weak. But for a large range of purposes it is valuable as a replacement for Basic Authentication. It remedies some, but not all, weaknesses of Basic Authentication. See RFC 2617, section 4. Security Considerations ( http://tools.ietf.org/html/rfc2617#section-4 ) for more information.
A buffer overflow in MySQL 5.0 through 5.0.54 and 5.1 before 5.1.23 contains a flaw in the protocol layer. A long error message can cause a buffer overflow, potentially leading to execution of code.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=32707 ( http://bugs.mysql.com/bug.php?id=32707 ) |
MySQL >= 5.0.0 and < 5.0.54
Upgrade to MySQL v5.0.54
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL server 5.0 before 5.0.67 contains a flaw in creating and dropping certain functions. Using MySQL's user-defined functions, an authenticated attacker can create a function in a shared library and run arbitrary code against the server.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=37428 ( http://bugs.mysql.com/bug.php?id=37428 ) |
MySQL >= 5.0.0 and < 5.0.67
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL 4.0.0 through 5.0.83 allow remote authenticated users to cause a denial of service (daemon crash) and possibly have unspecified other impact via format string specifiers in a database name in a (1) COM_CREATE_DB or (2) COM_DROP_DB request.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
35609 ( http://www.securityfocus.com/bid/35609 ) |
SECUNIA |
35767 ( http://secunia.com/advisories/35767/ ) |
XF |
mysql-dispatchcommand-format-string(51614) ( http://xforce.iss.net/xforce/xfdb/51614 ) |
CVE |
CVE-2009-2446 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-2446 ) |
MySQL >= 5.0.0 and < 5.0.84
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and daemon crash) by establishing an SSL connection and sending an X.509 client certificate with a crafted name field, as demonstrated by mysql_overflow1.py and the vd_mysql5 module in VulnDisco Pack Professional 8.11.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
37943 ( http://www.securityfocus.com/bid/37943 ) |
SECUNIA |
38364 ( http://secunia.com/advisories/38364/ ) |
XF |
mysql-unspecified-bo(55416) ( http://xforce.iss.net/xforce/xfdb/55416 ) |
CVE |
CVE-2009-4484 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-4484 ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-43.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-43.html ) |
URL |
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-90.html ( http://dev.mysql.com/doc/refman/5.0/en/news-5-0-90.html ) |
URL |
http://bugs.mysql.com/bug.php?id=50227 ( http://bugs.mysql.com/bug.php?id=50227 ) |
MySQL >= 5.0.0 and < 5.0.90
Upgrade to MySQL v5.0.90
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.43
Upgrade to MySQL v5.1.43
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
When configured with SSL support, MySQL 5.0.x before 5.0.54a, 5.1.x before 5.1.23, and 6.0.x before 6.0.4a is vulnerable to multiple buffer overflow vulnerabilities in the yaSSL package used to provide SSL support. The most severe of these vulnerabilities may allow unauthenticated remote code execution.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2008-0226 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-0226 ) |
CVE |
CVE-2008-0227 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-0227 ) |
URL |
http://bugs.mysql.com/bug.php?id=33814 ( http://bugs.mysql.com/bug.php?id=33814 ) |
BID |
27140 ( http://www.securityfocus.com/bid/27140 ) |
MySQL >= 5.0.0 and < 5.0.54a
Upgrade to MySQL v5.0.54a
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.4a
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Versions of MySQL server before 5.0.52 and 5.1.23 suffer from a denial of service vulnerability via a flaw in the federated engine. On issuance of a command to a remote server (e.g., SHOW TABLE STATUS LIKE 'table'), the local federated server expects a query to contain fourteen columns. A response with less than fourteen columns causes the federated server to crash.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=29801 ( http://bugs.mysql.com/bug.php?id=29801 ) |
MySQL >= 5.0.0 and < 5.0.52
Upgrade to MySQL v5.0.52
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
There is a flaw in parsing queries in MySQL 5.0 before 5.0.68 and MySQL 5.1 before 5.1.28. An attacker can potentially cause the server to crash by sending a query with multiple nested logic operators, e.g. 'SELECT * FROM TABLE WHERE ... OR ( ... OR ( ... OR ( ...' etc.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=38296 ( http://bugs.mysql.com/bug.php?id=38296 ) |
MySQL >= 5.0.0 and < 5.0.68
Upgrade to MySQL v5.0.68
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.28
Upgrade to MySQL v5.1.28
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
A buffer overflow in MySQL 5.0 before 5.0.91 and 5.1 before 5.1.47 allows remote authenticated users to execute arbitrary code via a COM_FIELD_LIST command with a long table name.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2010-1850 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1850 ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ) |
URL |
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-91.html ( http://dev.mysql.com/doc/refman/5.0/en/news-5-0-91.html ) |
URL |
http://bugs.mysql.com/bug.php?id=53237 ( http://bugs.mysql.com/bug.php?id=53237 ) |
MySQL >= 5.0.0 and < 5.0.91
Upgrade to MySQL v5.0.91
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.47
Upgrade to MySQL v5.1.47
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Directory traversal vulnerability in MySQL 5.0 before 5.0.91 and 5.1 before 5.1.47 allows remote authenticated users to bypass intended table grants to read field definitions of arbitrary tables, and on 5.1 to read or delete content of arbitrary tables, via a .. (dot dot) in a table name.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2010-1848 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1848 ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ) |
URL |
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-91.html ( http://dev.mysql.com/doc/refman/5.0/en/news-5-0-91.html ) |
URL |
http://bugs.mysql.com/bug.php?id=53371 ( http://bugs.mysql.com/bug.php?id=53371 ) |
MySQL >= 5.0.0 and < 5.0.91
Upgrade to MySQL v5.0.91
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.47
Upgrade to MySQL v5.1.47
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Certain versions of MySQL allow local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified DATA DIRECTORY or INDEX DIRECTORY arguments that are originally associated with pathnames without symlinks, and that can point to tables created at a future time at which a pathname is modified to contain a symlink to a subdirectory of the MySQL home data directory.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
29106 ( http://www.securityfocus.com/bid/29106 ) |
CVE |
CVE-2008-4097 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4097 ) |
CVE |
CVE-2008-4098 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4098 ) |
SECUNIA |
30134 ( http://secunia.com/advisories/30134/ ) |
URL |
http://bugs.mysql.com/bug.php?id=32167 ( http://bugs.mysql.com/bug.php?id=32167 ) |
URL |
http://lists.mysql.com/commits/50036 ( http://lists.mysql.com/commits/50036 ) |
URL |
http://lists.mysql.com/commits/50773 ( http://lists.mysql.com/commits/50773 ) |
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.10
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.32
Upgrade to MySQL v5.1.32
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.0.0 and < 5.0.68
Upgrade to MySQL v5.0.77
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^4.1.)
Upgrade to MySQL v4.1.25
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/4.1.html ( http://dev.mysql.com/downloads/mysql/4.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The vio_verify_callback function in viosslfactories.c in MySQL 5.0.x before 5.0.88 and 5.1.x before 5.1.41 accepts a value of zero for the depth of X.509 certificates when OpenSSL is used. This allows man-in-the-middle attackers to spoof arbitrary SSL-based MySQL servers via a crafted certificate.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2009-4028 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-4028 ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-41.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-41.html ) |
URL |
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-88.html ( http://dev.mysql.com/doc/refman/5.0/en/news-5-0-88.html ) |
URL |
http://bugs.mysql.com/bug.php?id=47320 ( http://bugs.mysql.com/bug.php?id=47320 ) |
MySQL >= 5.0.0 and < 5.0.88
Upgrade to MySQL v5.0.88
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.41
Upgrade to MySQL v5.1.41
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The subject common name (CN) field in the X.509 certificate does not match the name of the entity presenting the certificate.
Before issuing a certificate, a Certification Authority (CA) must check the identity of the entity requesting the certificate, as specified in the CA's Certification Practice Statement (CPS). Thus, standard certificate validation procedures require the subject CN field of a certificate to match the actual name of the entity presenting the certificate. For example, in a certificate presented by "https://www.example.com/", the CN should be "www.example.com".
In order to detect and prevent active eavesdropping attacks, the validity of a certificate must be verified, else an attacker could then launch a man-in-the-middle attack and gain full control of the data stream. Of particular importance is the validity of the subject's CN, that should match the name of the entity (hostname).
A CN mismatch most often occurs due to a configuration error, though it can also indicate that a man-in-the-middle attack is being conducted.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:443 |
The subject common name found in the X.509 certificate ('CN=Parallels Panel') does not seem to match the scan target 'vulnerable.plesk.smb.10.2.0.host':
|
vulnerable.plesk.smb.10.2.0.host:8443 |
The subject common name found in the X.509 certificate ('CN=Parallels Panel') does not seem to match the scan target 'vulnerable.plesk.smb.10.2.0.host':
|
None
The subject's common name (CN) field in the X.509 certificate should be fixed to reflect the name of the entity presenting the certificate (e.g., the hostname). This is done by generating a new certificate usually signed by a Certification Authority (CA) trusted by both the client and server.
The web application is vulnerable to cross-site scripting (XSS). Cross-site scripting vulnerabilities allow malicious attackers to take advantage of web server scripts to inject JavaScript or HTML code that is executed on the client-side browser. This is often caused by server-side scripts written in languages such as PHP, ASP, .NET, Perl or Java that do not adequately filter data sent along with page requests. This malicious code will appear to come from your web application when it runs in the browser of an unsuspecting user.
An exploit script can be made to:
The two most common methods of attack are:
In both scenarios, the URL will generally link to the trusted site, but will contain additional data that is used to trigger the XSS attack.
Note that SSL connectivity does not protect against this issue.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:8443 |
Injected into the "login_name" form parameter on https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ( https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ) : 28: turnAutocompleteOff(); 29: loff(); 30: var std_context = 'login_up'; 31: SetHelpPrefix(''); SetContext(std_context, ''); 32: ...ButtonByName(" |
vulnerable.plesk.smb.10.2.0.host:8443 |
Injected into the "passwd" form parameter on https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ( https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ) : 28: turnAutocompleteOff(); 29: loff(); 30: var std_context = 'login_up'; 31: SetHelpPrefix(''); SetContext(std_context, ''); 32: ...nByName("\'\'> |
vulnerable.plesk.smb.10.2.0.host:8443 |
Injected into the "passwd" form parameter on https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ( https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ) : 28: turnAutocompleteOff(); 29: loff(); 30: var std_context = 'login_up'; 31: SetHelpPrefix(''); SetContext(std_context, ''); 32: ...onByName("\'\' |
vulnerable.plesk.smb.10.2.0.host:8443 |
Injected into the "locale_id" form parameter on https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ( https://vulnerable.plesk.smb.10.2.0.host:8443/login_up.php3 ) : 28: turnAutocompleteOff(); 29: loff(); 30: var std_context = 'login_up'; 31: SetHelpPrefix(''); SetContext(std_context, ''); 32: ...ButtonByName(" |
Source |
Reference |
---|---|
CERT |
CA-2000-02 ( http://www.cert.org/advisories/CA-2000-02.html ) |
URL |
http://en.wikipedia.org/wiki/Cross_site_scripting ( http://en.wikipedia.org/wiki/Cross_site_scripting ) |
Audit the affected url and other similar dynamic pages or scripts that could be relaying untrusted malicious data from the user input. In general, the following practices should be followed while developing dynamic web content:
For more information on the above practices, read the following CERT advisory: CERT Advisory CA-2000-02 ( http://www.cert.org/tech_tips/malicious_code_mitigation.html )
For ASP.NET applications, the validateRequest attribute can be added to the page or the web.config. For example:
<%@ Page ... validateRequest="true" %> OR <system.web> <pages validateRequest="true" /> </system.web>
In addition, all dynamic content should be HTML encoded using HTTPUtility.HTMLEncode.
For PHP applications, input data should be validated using functions such as strip_tags and utf8_decode. Dynamic content should be HTML encoded using htmlentities.
For Perl applications, input data should be validated whenever possible using regular expressions. Dynamic content should be HTML encoded using HTML::Entities::encode or Apache::Util::html_encode (when using mod_perl).
MySQL 4.1.x before 4.1.24, 5.0.x before 5.0.60, 5.1.x before 5.1.24, and 6.0.x before 6.0.5 allows local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified (1) DATA DIRECTORY or (2) INDEX DIRECTORY arguments that are within the MySQL home data directory, which can point to tables that are created in the future.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2008-2079 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2079 ) |
URL |
http://dev.mysql.com/doc/refman/6.0/en/news-6-0-4.html ( http://dev.mysql.com/doc/refman/6.0/en/news-6-0-4.html ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.html ) |
URL |
http://bugs.mysql.com/32091 ( http://bugs.mysql.com/32091 ) |
XF |
mysql-datadirectory-privilege-escalation(38988) ( http://xforce.iss.net/xforce/xfdb/38988 ) |
MySQL (?:^4.1.)
Upgrade to MySQL v4.1.24
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/4.1.html ( http://dev.mysql.com/downloads/mysql/4.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.0.0 and < 5.0.60
Upgrade to MySQL v5.0.60
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.24
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.5
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Certain versions of MySQL do not correctly handle SQL requests containing empty literal bit-string, such as:
select b'';
This could allow a remote authenticated user to crash the service.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2008-3963 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-3963 ) |
SECUNIA |
31769 ( http://secunia.com/advisories/31769/ ) |
URL |
http://bugs.mysql.com/bug.php?id=35658 ( http://bugs.mysql.com/bug.php?id=35658 ) |
MySQL (?:^5.0.)
Upgrade to MySQL v5.0.66
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.26
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.6
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The federated engine in MySQL 5.0.x before 5.0.51a, 5.1.x before 5.1.23, and 6.0.x before 6.0.4, when performing a certain SHOW TABLE STATUS query, allows remote MySQL servers to cause a denial of service (federated handler crash and daemon crash) via a response that lacks the minimum required number of columns.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2007-6304 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-6304 ) |
BID |
26832 ( http://www.securityfocus.com/bid/26832 ) |
URL |
http://dev.mysql.com/doc/refman/6.0/en/news-6-0-4.html ( http://dev.mysql.com/doc/refman/6.0/en/news-6-0-4.html ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.html ) |
URL |
http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0-52.html ( http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0-52.html ) |
XF |
mysql-federated-engine-dos(38990) ( http://xforce.iss.net/xforce/xfdb/38990 ) |
MySQL (?:^5.0.)
Upgrade to MySQL v5.0.51a
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.4
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Although the server accepts clients using TLS or SSLv3, it also accepts clients using SSLv2. SSLv2 is an older implementation of the Secure Sockets Layer protocol. It suffers from a number of security flaws allowing attackers to capture and alter information passed between a client and the server, including the following weaknesses:
SSLv2 has been deprecated and is no longer recommended. Note that neither SSLv2 nor SSLv3 meet the U.S. FIPS 140-2 standard, which governs cryptographic modules for use in federal information systems. Only the newer TLS (Transport Layer Security) protocol meets FIPS 140-2 requirements. In addition, the presence of an SSLv2-only service on a host is deemed a failure by the PCI (Payment Card Industry) Data Security Standard.
Note that this vulnerability will be reported when the remote server supports SSLv2 regardless of whether TLS or SSLv3 are also supported.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:443 |
SSLv2 is supported |
vulnerable.plesk.smb.10.2.0.host:8443 |
SSLv2 is supported |
Source |
Reference |
---|---|
URL |
http://www.eucybervote.org/Reports/MSI-WP2-D7V1-V1.0-02.htm ( http://www.eucybervote.org/Reports/MSI-WP2-D7V1-V1.0-02.htm ) |
URL |
https://www.pcisecuritystandards.org/pdfs/pcissc_assessors_nl_2008-11.pdf ( https://www.pcisecuritystandards.org/pdfs/pcissc_assessors_nl_2008-11.pdf ) |
Configure the server to require clients to use at least SSLv3 or TLS.
For Microsoft IIS web servers, see Microsoft Knowledgebase article Q187498 ( http://support.microsoft.com/?id=187498 ) for instructions on disabling SSL 2.0.
For Apache web servers with mod_ssl, edit the Apache configuration file and change the SSLCipherSuite line to read:
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:!SSLv2
The ! (exclamation point) before SSLv2 is what disables this protocol.
A flaw in the ALTER VIEW routine of MySQL allows for the opportunity of an authenticated user to elevate their privileges in certain contexts.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=29908 ( http://bugs.mysql.com/bug.php?id=29908 ) |
MySQL >= 5.0.0 and < 5.0.52
Upgrade to MySQL v5.0.52
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Versions of MySQL server 5.0 before 5.0.84 and 5.1 before 5.1.36 suffer from a privilege interpretation flaw that causes a server crash. A user created with the privileges to create stored procedures but not execute them will trigger this issue.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
URL |
http://bugs.mysql.com/bug.php?id=44798 ( http://bugs.mysql.com/bug.php?id=44798 ) |
MySQL >= 5.0.0 and < 5.0.84
Upgrade to MySQL v5.0.84
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.36
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
Certain versions of MySQL contain an assertion error within the InnoDB engine. The convert_search_mode_to_innobase function in ha_innodb.cc allows remote authenticated users to cause a denial of service (database crash) with a query using CONTAINS on a column that does not support SPATIAL indexes.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
26353 ( http://www.securityfocus.com/bid/26353 ) |
CVE |
CVE-2007-5925 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-5925 ) |
SECUNIA |
27568 ( http://secunia.com/advisories/27568/ ) |
URL |
http://bugs.mysql.com/bug.php?id=32125 ( http://bugs.mysql.com/bug.php?id=32125 ) |
MySQL (?:^5.0.)
Upgrade to MySQL v5.0.24
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.4
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The my_net_skip_rest function in sql/net_serv.cc in MySQL 5.0 before 5.0.91 and 5.1 before 5.1.47 allows remote attackers to cause a denial of service (CPU and bandwidth consumption) by sending a large number of packets that exceed the maximum length.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
CVE |
CVE-2010-1849 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1849 ) |
URL |
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ( http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html ) |
URL |
http://bugs.mysql.com/bug.php?id=53371 ( http://bugs.mysql.com/bug.php?id=53371 ) |
URL |
http://bugs.mysql.com/bug.php?id=50974 ( http://bugs.mysql.com/bug.php?id=50974 ) |
MySQL >= 5.0.0 and < 5.0.91
Upgrade to MySQL v5.0.91
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL >= 5.1.0 and < 5.1.47
Upgrade to MySQL v5.1.47
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL Community Server 5.0.x before 5.0.51, Enterprise Server 5.0.x before 5.0.52, Server 5.1.x before 5.1.23, and Server 6.0.x before 6.0.4, when a table relies on symlinks created through explicit DATA DIRECTORY and INDEX DIRECTORY options, allows remote authenticated users to overwrite system table information and gain privileges via a RENAME TABLE statement that changes the symlink to point to an existing file.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
26765 ( http://www.securityfocus.com/bid/26765 ) |
CVE |
CVE-2007-5969 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-5969 ) |
SECUNIA |
27981 ( http://secunia.com/advisories/27981/ ) |
MySQL (?:^5.0.)
Upgrade to MySQL v5.0.51
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.0.html ( http://dev.mysql.com/downloads/mysql/5.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^5.1.)
Upgrade to MySQL v5.1.23
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
MySQL (?:^6.0.)
Upgrade to MySQL v6.0.4
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/6.0.html ( http://dev.mysql.com/downloads/mysql/6.0.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The server's TLS/SSL certificate is self-signed. Self-signed certificates cannot be trusted by default, especially because TLS/SSL man-in-the-middle attacks typically use self-signed certificates to eavesdrop on TLS/SSL connections.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:443 |
TLS/SSL certificate is self-signed. |
vulnerable.plesk.smb.10.2.0.host:8443 |
TLS/SSL certificate is self-signed. |
None
Obtain a new TLS/SSL server certificate that is NOT self-signed and install it on the server. The exact instructions for obtaining a new certificate depend on your organization's requirements. Generally, you will need to generate a certificate request and save the request as a file. This file is then sent to a Certificate Authority (CA) for processing. Your organization may have its own internal Certificate Authority. If not, you may have to pay for a certificate from a trusted external Certificate Authority, such as Thawte ( http://www.thawte.com ) or Verisign ( http://www.verisign.com ) .
Microsoft IIS supports Basic and NTLM authentication. The authentication methods supported by a given IIS server can be revealed to an attacker through the inspection of returned error messages, even when anonymous access is also granted.
When a valid authentication request is submitted for either message with an invalid username and password, an error message will be returned. This happens even if anonymous access to the requested resource is allowed. An attacker may be able to use this information to launch further intelligent attacks against the server, or to launch a brute force password attack against a known user name.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:80 |
The server responded with a 401/Unauthorized error code when requesting: http://vulnerable.plesk.smb.10.2.0.host:80/ ( http://vulnerable.plesk.smb.10.2.0.host:80/ ) with the header:Authorization: Negotiate TlRMTVNTUAABAAAAB4IoAAAAAAAAAAAAAAAAAAAAAA= |
vulnerable.plesk.smb.10.2.0.host:8443 |
The server responded with a 401/Unauthorized error code when requesting: https://vulnerable.plesk.smb.10.2.0.host:8443/ ( https://vulnerable.plesk.smb.10.2.0.host:8443/ ) with the header:Authorization: Negotiate TlRMTVNTUAABAAAAB4IoAAAAAAAAAAAAAAAAAAAAAA= |
Source |
Reference |
---|---|
CVE |
CVE-2002-0419 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2002-0419 ) |
BID |
4235 ( http://www.securityfocus.com/bid/4235 ) |
If the server is intended for public use then it may be possible to simply disable both basic and integrated Windows authentication. Sites that use form-based logins when users are authenticated against a database and track logged in users with cookies will be able to disable these authentication methods. Doing this will prevent such attacks.
If basic or integrated Windows authentication is required on the server, these steps should be considered:
A cross-site scripting (XSS) vulnerability exists in the command-line client when the "--html" option is enabled. This could allow attackers to inject arbitrary web script or HTML by placing it in a database cell, which might be accessed by the client when composing an HTML document.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service: MySQL 5.0.45. |
Source |
Reference |
---|---|
BID |
31486 ( http://www.securityfocus.com/bid/31486 ) |
CVE |
CVE-2008-4456 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4456 ) |
SECUNIA |
32072 ( http://secunia.com/advisories/32072/ ) |
URL |
http://bugs.mysql.com/bug.php?id=27884 ( http://bugs.mysql.com/bug.php?id=27884 ) |
URL |
http://www.henlich.de/it-security/mysql-command-line-client-html-injection-vulnerability ( http://www.henlich.de/it-security/mysql-command-line-client-html-injection-vulnerability ) |
MySQL (?:^5.1.)
Download and apply the upgrade from: http://dev.mysql.com/downloads/mysql/5.1.html ( http://dev.mysql.com/downloads/mysql/5.1.html )
Please note that individual platforms and OS distributions may provide their own means of upgrading MySQL (via an RPM, for example). These supported upgrade methods should be used if available, instead of building the distribution from scratch.
The remote host responded to an ICMP timestamp request. The ICMP timestamp response contains the remote host's date and time. This information could theoretically be used against some systems to exploit weak time-based random number generators in other services.
In addition, the versions of some operating systems can be accurately fingerprinted by analyzing their responses to invalid ICMP timestamp requests.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host |
Remote system time: 12:04:06.000 EDT |
Source |
Reference |
---|---|
XF |
icmp-timestamp(322) ( http://xforce.iss.net/xforce/xfdb/322 ) |
CVE |
CVE-1999-0524 ( http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 ) |
HP-UX
Disable ICMP timestamp responses on HP/UX
Execute the following command:
ndd -set /dev/ip ip_respond_to_timestamp_broadcast 0
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Cisco IOS
Disable ICMP timestamp responses on Cisco IOS
Use ACLs to block ICMP types 13 and 14. For example:
deny icmp any any 13
deny icmp any any 14
Note that it is generally preferable to use ACLs that block everything by default and then selectively allow certain types of traffic in. For example, block everything and then only allow ICMP unreachable, ICMP echo reply, ICMP time exceeded, and ICMP source quench:
permit icmp any any unreachable
permit icmp any any echo-reply
permit icmp any any time-exceeded
permit icmp any any source-quench
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
SGI Irix
Disable ICMP timestamp responses on SGI Irix
IRIX does not offer a way to disable ICMP timestamp responses. Therefore, you should block ICMP on the affected host using ipfilterd, and/or block it at any external firewalls.
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Linux
Disable ICMP timestamp responses on Linux
Linux offers neither a sysctl nor a /proc/sys/net/ipv4 interface to disable ICMP timestamp responses. Therefore, you should block ICMP on the affected host using iptables, and/or block it at the firewall. For example:
ipchains -A input -p icmp --icmp-type timestamp-request -j DROP
ipchains -A output -p icmp --icmp-type timestamp-reply -j DROP
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Microsoft Windows NT, Microsoft Windows NT Workstation, Microsoft Windows NT Server, Microsoft Windows NT Advanced Server, Microsoft Windows NT Server, Enterprise Edition, Microsoft Windows NT Server, Terminal Server Edition
Disable ICMP timestamp responses on Windows NT 4
Windows NT 4 does not provide a way to block ICMP packets. Therefore, you should block them at the firewall.
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
OpenBSD
Disable ICMP timestamp responses on OpenBSD
Set the "net.inet.icmp.tstamprepl" sysctl variable to 0.
sysctl -w net.inet.icmp.tstamprepl=0
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Cisco PIX
Disable ICMP timestamp responses on Cisco PIX
A properly configured PIX firewall should never respond to ICMP packets on its external interface. In PIX Software versions 4.1(6) until 5.2.1, ICMP traffic to the PIX's internal interface is permitted; the PIX cannot be configured to NOT respond. Beginning in PIX Software version 5.2.1, ICMP is still permitted on the internal interface by default, but ICMP responses from its internal interfaces can be disabled with the icmp command, as follows, where <inside> is the name of the internal interface:
icmp deny any 13 <inside>
icmp deny any 14 <inside>
Don't forget to save the configuration when you are finished.
See Cisco's support document Handling ICMP Pings with the PIX Firewall ( http://www.cisco.com/warp/public/110/31.html ) for more information.
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Sun Solaris
Disable ICMP timestamp responses on Solaris
Execute the following commands:
/usr/sbin/ndd -set /dev/ip ip_respond_to_timestamp 0
/usr/sbin/ndd -set /dev/ip ip_respond_to_timestamp_broadcast 0
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Microsoft Windows 2000, Microsoft Windows 2000 Professional, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server
Disable ICMP timestamp responses on Windows 2000
Use the IPSec filter feature to define an apply an IP filter list that blocks ICMP types 13 and 14. Note that the standard TCP/IP blocking capability under the "Networking and Dialup Connections" control panel is NOT capable of blocking ICMP (only TCP and UDP). The IPSec filter features, while they may seem strictly related to the IPSec standards, will allow you to selectively block these ICMP packets. See http://support.microsoft.com/kb/313190 ( http://support.microsoft.com/kb/313190 ) for more information.
The easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
Microsoft Windows XP, Microsoft Windows XP Home, Microsoft Windows XP Professional, Microsoft Windows Server 2003, Microsoft Windows Server 2003, Standard Edition, Microsoft Windows Server 2003, Enterprise Edition, Microsoft Windows Server 2003, Datacenter Edition, Microsoft Windows Server 2003, Web Edition, Microsoft Windows Small Business Server 2003
Disable ICMP timestamp responses on Windows XP/2K3
ICMP timestamp responses can be disabled by deselecting the "allow incoming timestamp request" option in the ICMP configuration panel of Windows Firewall.
For more information, see: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/hnw_understanding_firewall.mspx?mfr=true ( http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/hnw_understanding_firewall.mspx?mfr=true )
Microsoft Windows Vista, Microsoft Windows Vista Home, Basic Edition, Microsoft Windows Vista Home, Basic N Edition, Microsoft Windows Vista Home, Premium Edition, Microsoft Windows Vista Ultimate Edition, Microsoft Windows Vista Enterprise Edition, Microsoft Windows Vista Business Edition, Microsoft Windows Vista Business N Edition, Microsoft Windows Vista Starter Edition, Microsoft Windows Server 2008, Microsoft Windows Server 2008 Standard Edition, Microsoft Windows Server 2008 Enterprise Edition, Microsoft Windows Server 2008 Datacenter Edition, Microsoft Windows Server 2008 HPC Edition, Microsoft Windows Server 2008 Web Edition, Microsoft Windows Server 2008 Storage Edition, Microsoft Windows Small Business Server 2008, Microsoft Windows Essential Business Server 2008
Disable ICMP timestamp responses on Windows Vista/2008
ICMP timestamp responses can be disabled via the netsh command line utility.
For more information, see: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/hnw_understanding_firewall.mspx?mfr=true ( http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/hnw_understanding_firewall.mspx?mfr=true )
Disable ICMP timestamp responses
Disable ICMP timestamp replies for the device. If the device does not support this level of configuration, the easiest and most effective solution is to configure your firewall to block incoming and outgoing ICMP packets with ICMP types 13 (timestamp request) and 14 (timestamp response).
The database allows any remote system the ability to connect to it. It is recommended to limit direct access to trusted systems because databases may contain sensitive data, and new vulnerabilities and exploits are discovered routinely for them. For this reason, it is a violation of PCI DSS section 1.3.7 to have databases listening on ports accessible from the Internet, even when protected with secure authentication mechanisms.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:3306 |
Running vulnerable MySQL service. |
Source |
Reference |
---|---|
URL |
https://www.pcisecuritystandards.org/security_standards/download.html?id=pci_dss_v1-2.pdf ( https://www.pcisecuritystandards.org/security_standards/download.html?id=pci_dss_v1-2.pdf ) |
Configure the database server to only allow access to trusted systems. For example, the PCI DSS standard requires to place the database in an internal network zone, segregated from the DMZ
WebDAV is a set of extensions to the HTTP protocol that allows users to collaboratively edit and manage files on remote web servers. Many web servers enable WebDAV extensions by default, even when they are not needed. Because of its added complexity, it is considered good practice to disable WebDAV if it is not currently in use.
Affected Nodes: |
Additional Information: |
---|---|
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/common/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/css/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/css/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/images/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/images/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/apps/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/apps/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/common/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/glyph/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/glyph/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/icons/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/icons/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/include/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:80 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/include/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/css/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/apps/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/apps/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/common/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/common/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/glyph/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/glyph/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/icons/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/img/icons/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/include/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/include/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/images/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/images/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/css/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/', it is apparent that WebDAV is enabled. |
vulnerable.plesk.smb.10.2.0.host:443 |
Because the HTTP methods 'GET, HEAD, OPTIONS, TRACE, COPY, PROPFIND, LOCK, UNLOCK' were found in the OPTIONS response on the directory '/', it is apparent that WebDAV is enabled. |
Source |
Reference |
---|---|
URL |
http://www.nextgenss.com/papers/iisrconfig.pdf ( http://www.nextgenss.com/papers/iisrconfig.pdf ) |
IIS, PWS, Microsoft-IIS, Internet Information Server, Internet Information Services, Microsoft-PWS
Disable WebDAV for IIS
For Microsoft IIS, follow Microsoft's instructions ( http://support.microsoft.com/default.aspx?kbid=241520 ) to disable WebDAV for the entire server.
Apache
Disable WebDAV for Apache
Make sure the mod_dav module is disabled, or ensure that authentication is required on directories where DAV is required.
Apache Tomcat, Tomcat, Tomcat Web Server
Disable WebDAV for Apache Tomcat
Disable the WebDAV Servlet for all web applications found on the web server. This can be done by removing the servlet definition for WebDAV (the org.apache.catalina.servlets.WebdavServlet class) and remove all servlet mappings referring to the WebDAV servlet.
Java System Web Server, iPlanet, SunONE WebServer, Sun-ONE-Web-Server
Disable WebDAV for iPlanet/Sun ONE
Disable WebDAV on the web server. This can be done by disabling WebDAV for the server instance and for all virtual servers.
To disable WebDAV for the server instance, enter the Server Manager and uncheck the "Enable WebDAV Globally" checkbox then click the "OK" button.
To disable WebDAV for each virtual server, enter the Class Manager and uncheck the "Enable WebDAV Globally" checkbox next to each server instance then click the "OK" button.
DNS, the Domain Name System, provides naming services on the Internet. DNS is primarily used to convert names, such as www.rapid7.com to their corresponding IP address for use by network programs, such as a browser.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
udp |
53 |
0 |
DNS, the Domain Name System, provides naming services on the Internet. DNS is primarily used to convert names, such as www.rapid7.com to their corresponding IP address for use by network programs, such as a browser. This service is used primarily for zone transfers between DNS servers. It can, however, be used for standard DNS queries as well.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
53 |
0 |
FTP, the File Transfer Protocol, is used to transfer files between systems. On the Internet, it is often used on web pages to download files from a web site using a browser. FTP uses two connections, one for control connections used to authenticate, navigate the FTP server and initiate file transfers. The other connection is used to transfer data, such as files or directory listings.
The original FTP specification only provided means for authentication with cleartext user ids and passwords. Though FTP has added support for more secure mechanisms such as Kerberos, cleartext authentication is still the primary mechanism. If a malicious user is in a position to monitor FTP traffic, user ids and passwords can be stolen.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
21 |
0 |
|
HTTP, the HyperText Transfer Protocol, is used to exchange multimedia content on the World Wide Web. The multimedia files commonly used with HTTP include text, sound, images and video.
Many HTTP servers use BASIC as their primary mechanism for user authentication. This is a very simple scheme that uses base 64 to encode the cleartext user id and password. If a malicious user is in a position to monitor HTTP traffic, user ids and passwords can be stolen by decoding the base 64 authentication data. To secure the authentication process, use HTTPS (HTTP over TLS/SSL) connections to transmit the authentication data.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
80 |
3 |
|
HTTPS, the HyperText Transfer Protocol over TLS/SSL, is used to exchange multimedia content on the World Wide Web using encrypted (TLS/SSL) connections. Once the TLS/SSL connection is established, the standard HTTP protocol is used. The multimedia files commonly used with HTTP include text, sound, images and video.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
443 |
3 |
|
vulnerable.plesk.smb.10.2.0.host |
tcp |
8443 |
3 |
|
IMAP, the Interactive Mail Access Protocol or Internet Message Access Protocol, is used to access and manipulate electronic mail (e-mail). IMAP servers can contain several folders, aka mailboxes, containing messages (e-mails) for users.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
143 |
0 |
|
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
3389 |
0 |
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
3306 |
6 |
|
The Post Office Protocol allows workstations to retrieve e-mail dynamically from a mailbox server.
Device |
Protocol |
Port |
Vulnerabilities |
Additional Information |
---|---|---|---|---|
vulnerable.plesk.smb.10.2.0.host |
tcp |
110 |
0 |
|
No user or group information was discovered during the scan.
No database information was discovered during the scan.
No file or directory information was discovered during the scan.
No policy evaluations were performed.
The following URLs were guessed. They are often included with default web server or web server add-on installations.
The following URLs were guessed using various tricks based on the discovered web site content.
The following URLs were found as links in the content of other web pages.
The following URLs were guessed. They are often included with default web server or web server add-on installations.
The following URLs were guessed using various tricks based on the discovered web site content.
The following URLs were found as links in the content of other web pages.
The following URLs were guessed. They are often included with default web server or web server add-on installations.
The following URLs were guessed using various tricks based on the discovered web site content.
The following URLs were found as links in the content of other web pages.