prototype-pollution.md

Protect against prototype pollution

Aikido runtime can also protect your application against prototype pollution attacks.

It works by calling Object.freeze for some built-in JavaScript objects.

The Object.freeze() method freezes an object. A frozen object can no longer be changed; freezing an object prevents new properties from being added to it, existing properties from being removed, prevents changing the enumerability, configurability, or writability of existing properties, and prevents the values of existing properties from being changed.

We believe that there are legitimate cases of prototype changes, but they should happen only during the initialization step. Hence, we recommend requiring @aikidosec/runtime/nopp after your main imports.

const express = require('express');

require('@aikidosec/runtime/nopp'); // <-- Include this after your main imports

const app = express();

app.get("/", (req, res) => {
  res.send("Hello, world!");
});

app.listen(3000, () => {
  console.log("Server is running on port 3000");
});

or ESM import style:

import '@aikidosec/runtime/nopp';

together with protect:

import '@aikidosec/runtime'; // <-- Include this before any other code or imports

import express from 'express';

import '@aikidosec/runtime/nopp'; // <-- Include this after your main imports

// ...

WARNING: Read this before using @aikidosec/runtime/nopp

This might break your application or result in strange errors if you are using libraries that rely on changing the prototype of built-in objects after your application has started. We recommend testing your application thoroughly after including @aikidosec/runtime/nopp.

You should enable this on your staging environment for a considerable amount of time before enabling it on your production environment (e.g. one week).

Incompatible packages

Some packages may not work properly when @aikidosec/runtime/nopp is required, these are some of the known packages:

• mongoose (versions 1.x to 4.x)