Express Prototype Pollution Gadgets

Serve XSS responses

Change JSON content-type to HTML

In an Express app using a JSON content type response and reflecting a JSON:
app.use(bodyParser.json({type: 'application/json'}));'/', function(req, res){
_.merge({}, req.body);
In these cases XSS isn't normally possible with a JSON content type. However, with prototype pollution we can confuse Express to serve up an HTML response. This vulnerability relies on the application using res.send(obj) and using the body parser with the application/json content type.
By polluting both the body and _body properties, it's possible to cause Express to serve up the HTML content type and reflect the _body property, resulting in stored XSS.

Render UTF7

It's possible to make express render UTF-7 content with:
{"__proto__":{"content-type": "application/json; charset=utf-7"}}

Safe Scanning Techinques

JSON spaces

The following PP will make attributes inside a JSON to have an extra space which won't break the functionality:
{"__proto__":{"json spaces": " "}}
Then a reflected JSON will looks like:
{"foo": "bar"} -- Note the extra space

Exposed Headers

The following PP gadget will make the server send back the HTTP header: Access-Control-Expose_headers: foo
It requires the CORS module to be installed


With the following payload, it's possible to hide a method from an OPTIONS response:
// Original reponse: POST,GET,HEAD
// Payload:
//New response: POST;GET


It's possible to change the returned status code using the following PP payload:


When you assign to a prototype with a primitive such as a string, it produces a no-op operation since the prototype has to be an object. If you attempt to assign a prototype object to the Object.prototype itself, this will throw an exception. We can use these two behaviours to detect if prototype pollution was successful:
({}).__proto__.__proto__={}//throws type exception
({}).__proto__.__proto__="x"//no-op does not throw exception

Reflected Value

If the application is reflecting an object in the response you could just create an attribute with a weird name and the __proto__ one and if only the weird one is reflected is possible that the web is vulnerable:
Or if Lodash or similar library is used, you can set a property via PP and inside the object and if that property is not reflected is because Lodash looks at the current object to see if the property already exists in the merged object:
// If only b is reflected then PP in Lodash


Allow Dots

There is an option in Express that allows you to create objects from query string parameters. You could definitely use it in a bug chain to exploit a prototype pollution vulnerability.
? create an object in Node.