XSS Filter Bypass via Encoded URL in validator
Versions of `validator` prior to 2.0.0 contained an xss filter method that is affected by several filter bypasses. This may result in a cross-site scripting vulnerability. ## Proof of Concept The xss() function removes the word "javascript" when contained inside an attribute. However, it does not properly handle cases where characters have been hex-encoded. As a result, it is possible to build an input that bypasses the filter but which the browser will accept as valid JavaScript. For example: ```<a href="javascript:...">abc</a>``` will render as: ```<a href="javascript:...">abc</a>``` ## Recommendation The package author has decided to remove the xss filter functionality in the latest version of this module. If this feature is not currently being used, you are not affected by the vulnerability. If it is being used, updating to the latest version of the module will break your application. In order for affected users to mitigate this vulnerability, it is necessary to use an [alternative package](https://www.npmjs.com/search?q=xss%20filter&page=1&ranking=optimal) that provides similar functionality.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-9772US | medium6.1 | — | ||
The validator package before 2.0.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via hex-encoded characters. | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2016/04/20/11WEB
- http://www.securityfocus.com/bid/97102WEB
- https://github.com/advisories/GHSA-79mx-88w7-8f7qADVISORY
- https://github.com/chriso/validator.jsPACKAGE
- https://github.com/chriso/validator.js/issues/181WEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-9772ADVISORY
- https://www.npmjs.com/advisories/43WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan