SQL Injection, Single Quote DORK, CWE-89, bvtservices.com

The articleid parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the articleid parameter, 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 MySQL.

Remediation detail

The application should handle errors gracefully and prevent SQL error messages from being returned in responses.

Issue background

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.

Request 1

GET /content.php?articleid=50' HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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 1

HTTP/1.1 200 OK
Date: Fri, 11 Mar 2011 12:52:39 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 3863

<html>
<head>
<title>ContentMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, host
...[SNIP]...
</b>: 1064 (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''50''' at line 1)<br>
...[SNIP]...

Request 2

GET /content.php?articleid=50'' HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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 2

2. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/content.php

Issue detail

The page was loaded from a URL containing a query string:

http://www.bvtservices.com/content.php?articleid=50

The response contains the following links to other domains:

http://jerz.setonhill.edu/writing/e-text/e-mail.htm
http://owl.english.purdue.edu/owl/resource/636/01/
http://secureflorida.org/emailpractices/email_safety_tips/
http://thinksimplenow.com/productivity/15-tips-for-writing-effective-email/
http://www.101emailetiquettetips.com/
http://www.archives.nysed.gov/a/records/mr_pub62.shtml
http://www.care2.com/help/email/compose.html
http://www.datehookup.com/content-email-tips-for-beginners.htm
http://www.itsecurity.com/features/99-email-security-tips-112006/
http://www.lifehack.org/articles/technology/10-simple-tips-for-using-email.html
http://www.linuxplanet.com/linuxplanet/tips/6833/1/
http://www.mindtools.com/CommSkll/EmailCommunication.htm
http://www.pcworld.com/article/18324/managing_the_email_explosion.html
http://www.stanford.edu/~pgbovine/email-tips.htm
http://www.us-cert.gov/cas/tips/ST04-007.html
http://www.webfoot.com/advice/email.gestures.php

Issue background

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.

Request

GET /content.php?articleid=50 HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:38 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 11458

<html>
<head>
<title>ContentMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, host
...[SNIP]...
<br>
<a href="http://www.datehookup.com/content-email-tips-for-beginners.htm" target="exlink4">http://www.datehookup.com/content-email-tips-for-beginners.htm</a>
...[SNIP]...
<li><a href="http://www.care2.com/help/email/compose.html" rel="nofollow" target="exa1">Know The Basics</a>
...[SNIP]...
<li><a href="http://jerz.setonhill.edu/writing/e-text/e-mail.htm#subject" rel="nofollow" target="exa2">Make the Subject Line Concise</a>
...[SNIP]...
<li><a href="http://www.101emailetiquettetips.com/" rel="nofollow" target="exa3">Use Proper Etiquette</a>
...[SNIP]...
<li><a href="http://www.mindtools.com/CommSkll/EmailCommunication.htm" rel="nofollow" target="exa4">Make Each Email a Separate Point</a>
...[SNIP]...
<li><a href="http://www.lifehack.org/articles/technology/10-simple-tips-for-using-email.html" rel="nofollow" target="exa5">Use Different Accounts</a>
...[SNIP]...
<li><a href="http://www.itsecurity.com/features/99-email-security-tips-112006/" rel="nofollow" target="exa6">Do Not Send Chain Emails</a>
...[SNIP]...
<li><a href="http://www.stanford.edu/%7Epgbovine/email-tips.htm" rel="nofollow" target="exa7">Stay Professional</a>
...[SNIP]...
<li><a href="http://www.webfoot.com/advice/email.gestures.php" rel="nofollow" target="exa8">Be Web-Savvy in Your Emails</a>
...[SNIP]...
<li><a href="http://www.linuxplanet.com/linuxplanet/tips/6833/1/" rel="nofollow" target="exa9">Utilize Your Email's Tools</a>
...[SNIP]...
<li><a href="http://thinksimplenow.com/productivity/15-tips-for-writing-effective-email/" rel="nofollow" target="exa10">Understand the Psycholgy</a>
...[SNIP]...
<li><a href="http://www.pcworld.com/article/18324/managing_the_email_explosion.html" rel="nofollow" target="exa11">Stay Organized</a>
...[SNIP]...
<li><a href="http://www.archives.nysed.gov/a/records/mr_pub62.shtml" rel="nofollow" target="exa12">Keep Your In-Box Clean</a>
...[SNIP]...
<li> <a href="http://owl.english.purdue.edu/owl/resource/636/01/" rel="nofollow" target="exa13">Know What NOT To Include</a>
...[SNIP]...
<li><a href="http://secureflorida.org/emailpractices/email_safety_tips/" rel="nofollow" target="exa14">Be Safe</a>
...[SNIP]...
<p><a href="http://www.us-cert.gov/cas/tips/ST04-007.html" rel="nofollow">Reduce the SPAM</a>
...[SNIP]...

3. Email addresses disclosed previous next
There are 6 instances of this issue:

/
/content.php
/frameset.php
/navbar.php
/news.php
/topbar.php

Issue background

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).

3.1. http://www.bvtservices.com/ next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/

Issue detail

The following email addresses were disclosed in the response:

info@BVTServices.Com
info@bvtservices.com

Request

GET / HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://burlingtonvt.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:24 GMT
Server: Apache/2.0.46 (CentOS)
Last-Modified: Wed, 30 Mar 2005 21:06:09 GMT
ETag: "22804d-d8c-256df240"
Accept-Ranges: bytes
Content-Length: 3468
Connection: close
Content-Type: text/html

<html>
<head>
<title>BVT Services - Premiere Hosting, Information Technology Services, and Support</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burl
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...

3.2. http://www.bvtservices.com/content.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/content.php

Issue detail

The following email addresses were disclosed in the response:

Info@BVTServices.Com
Support@BVTServices.Com
info@BVTServices.Com
info@bvtservices.com

Request

GET /content.php?articleid=4 HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/topbar.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:53:47 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 5767

<html>
<head>
<title>ContentMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, host
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...
<a href="mailto:Support@BVTServices.Com">Support@BVTServices.Com</a>
...[SNIP]...
<a href="mailto:Info@BVTServices.Com">Info@BVTServices.Com</a>
...[SNIP]...

3.3. http://www.bvtservices.com/frameset.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/frameset.php

Issue detail

The following email addresses were disclosed in the response:

info@BVTServices.Com
info@bvtservices.com

Request

GET /frameset.php HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:32 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 1579

<html>
<head>
<title>BVT Services - Premiere Hosting, Information Technology Services, and Support</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Bur
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...

3.4. http://www.bvtservices.com/navbar.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/navbar.php

Issue detail

The following email addresses were disclosed in the response:

info@BVTServices.Com
info@bvtservices.com

Request

GET /navbar.php HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/frameset.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 9348

<html>
<head>
<title>MainNavMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, host
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...

3.5. http://www.bvtservices.com/news.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/news.php

Issue detail

The following email addresses were disclosed in the response:

info@BVTServices.Com
info@bvtservices.com

Request

GET /news.php HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/frameset.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 2576

<HTML>
<head>
<title>NewsMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, BVTServices.Com, BVTServices,Com, BVTServices, BVT Services, BVT, hosting,
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...

3.6. http://www.bvtservices.com/topbar.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/topbar.php

Issue detail

The following email addresses were disclosed in the response:

info@BVTServices.Com
info@bvtservices.com

Request

GET /topbar.php HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/frameset.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 3961

<HTML>
<head>
<title>TopNavMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, hosti
...[SNIP]...
<meta name="publisher-email" CONTENT="info@bvtservices.com">
...[SNIP]...
<meta name="author" content="info@BVTServices.Com, http://www.BVTServices.Com">
...[SNIP]...

4. HTML does not specify charset previous next
There are 6 instances of this issue:

/
/content.php
/frameset.php
/navbar.php
/news.php
/topbar.php

Issue description

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.

4.1. http://www.bvtservices.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/

Request

Response

4.2. http://www.bvtservices.com/content.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/content.php

Request

GET /content.php HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/frameset.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 12915

<html>
<head>
<title>ContentMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, host
...[SNIP]...

4.3. http://www.bvtservices.com/frameset.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/frameset.php

Request

Response

4.4. http://www.bvtservices.com/navbar.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/navbar.php

Request

Response

4.5. http://www.bvtservices.com/news.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/news.php

Request

Response

HTTP/1.1 200 OK
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 2576

<HTML>
<head>
<title>NewsMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, BVTServices.Com, BVTServices,Com, BVTServices, BVT Services, BVT, hosting,
...[SNIP]...

4.6. http://www.bvtservices.com/topbar.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.bvtservices.com
Path:	/topbar.php

Request

Response

HTTP/1.1 200 OK
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Accept-Ranges: bytes
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
Content-Length: 3961

<HTML>
<head>
<title>TopNavMod</title>
<meta name="robots" content="INDEX">
<meta name="keywords" content="Vermont, Burlington, Burlingtonvt.com, BVTServices,Com, BVTServices, BVT Services, BVT, hosti
...[SNIP]...

5. Content type incorrectly stated previous
There are 4 instances of this issue:

/css/style.txt
/favicon.ico
/images/scrollDown.jpg
/images/scrollUp.jpg

Issue background

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.

5.1. http://www.bvtservices.com/css/style.txt previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.bvtservices.com
Path:	/css/style.txt

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

The response states that it contains plain text. However, it actually appears to contain HTML.

Request

GET /css/style.txt HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/news.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: text/css,*/*;q=0.1
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Last-Modified: Wed, 15 Jan 2003 23:13:57 GMT
ETag: "4600b6-638-18397740"
Accept-Ranges: bytes
Content-Length: 1592
Connection: close
Content-Type: text/plain

<style>
<!--
A { font-family: Arial, Helvetica, sans-serif; font-size: 10px; font-weight: 400; color: #000000; text-decoration: none}
.copyBold { font-family: Arial, Helvetica, sans-serif; font-size
...[SNIP]...

5.2. http://www.bvtservices.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.bvtservices.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Request

GET /favicon.ico HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
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
Date: Fri, 11 Mar 2011 12:52:24 GMT
Server: Apache/2.0.46 (CentOS)
Last-Modified: Wed, 15 Jan 2003 23:12:40 GMT
ETag: "228082-37e-13a28a00"
Accept-Ranges: bytes
Content-Length: 894
Connection: close
Content-Type: text/plain

..............h.......(....... .........................................................................................................................................................................
...[SNIP]...

5.3. http://www.bvtservices.com/images/scrollDown.jpg previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.bvtservices.com
Path:	/images/scrollDown.jpg

Issue detail

The response contains the following Content-type statement:

Content-Type: image/jpeg

The response states that it contains a JPEG image. However, it actually appears to contain a GIF image.

Request

GET /images/scrollDown.jpg HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/content.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: */*
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Last-Modified: Wed, 15 Jan 2003 23:14:03 GMT
ETag: "500060-73-189504c0"
Accept-Ranges: bytes
Content-Length: 115
Connection: close
Content-Type: image/jpeg

GIF89a.......1k............................................,........(..Ii.8...........y.b...'..`.'\.y...Qe(...;

5.4. http://www.bvtservices.com/images/scrollUp.jpg previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.bvtservices.com
Path:	/images/scrollUp.jpg

Issue detail

The response contains the following Content-type statement:

Content-Type: image/jpeg

The response states that it contains a JPEG image. However, it actually appears to contain a GIF image.

Request

GET /images/scrollUp.jpg HTTP/1.1
Host: www.bvtservices.com
Proxy-Connection: keep-alive
Referer: http://www.bvtservices.com/content.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16
Accept: */*
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
Date: Fri, 11 Mar 2011 12:52:33 GMT
Server: Apache/2.0.46 (CentOS)
Last-Modified: Wed, 15 Jan 2003 23:14:03 GMT
ETag: "500061-74-189504c0"
Accept-Ranges: bytes
Content-Length: 116
Connection: close
Content-Type: image/jpeg

GIF89a.......1k............................................,........)..Ii.8..... f` ..8z..\. _.L.Y.....;..B.D..;

Report generated by XSS.CX Research Blog at Fri Mar 11 06:58:04 CST 2011.