Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.

Affected: npm: url-parse

Leading control characters in a URL are not stripped when passed into url-parse. This can cause input URLs to be mistakenly be interpreted as a relative URL without a hostname and protocol, while the WHATWG URL parser will trim control characters and treat it as an absolute URL.

If url-parse is used in security decisions involving the hostname / protocol, and the input URL is used in a client which uses the WHATWG URL parser, the decision may be incorrect.

This can also lead to a cross-site scripting (XSS) vulnerability if url-parse is used to check for the javascript: protocol in URLs. See following example: ```js const parse = require('url-parse') const express = require('express') const app = express() const port = 3000

url = parse(\"\\bjavascript:alert(1)\")

console.log(url)

app.get('/', (req, res) => { if (url.protocol !== \"javascript:\") {res.send(\"<a href=\\'\" + url.href + \"\\'>CLICK ME!</a>\")} })

app.listen(port, () => { console.log(`Example app listening on port ${port}`) }) ```

nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions nodejs-lodash: command injection via template nodejs-url-parse: authorization bypass through user-controlled key npm-url-parse: Authorization Bypass Through User-Controlled Key npm-url-parse: Authorization bypass through user-controlled key npm-url-parse: authorization bypass through user-controlled key eventsource: Exposure of Sensitive Information golang: compress/gzip: stack exhaustion in Reader.Read

Affected: Ubuntu:Pro:16.04:LTS: node-url-parse, Ubuntu:18.04:LTS: node-url-parse, Ubuntu:20.04:LTS: node-url-parse

Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.