GHSA-2gqw-q9r9-7f79 Changeset vulnerable to prototype pollution

• npm changeset: >= 0.0.1, < 0.2.5 → fixed in 0.2.5

Overview Prototype pollution vulnerability in 'changeset' versions 0.0.1 through 0.2.5 allows attackers to cause a denial of service and may lead to remote code execution. Details The npm module 'changeset' can be abused by Prototype Pollution vulnerability since the function 'apply()' does not check for the type of object before assigning value to the property. Due to this flaw an attacker could create a non-existent property or able to manipulate the property which leads to Denial of Service or potentially Remote code execution. PoC Details The 'apply()' function accepts 'changes, target, modify' as argument. Due to the absence of validation on the values passed into the 'changes' argument, an attacker can supply a malicious value by adjusting the value to include the '__proto__' property. Since there is no validation before assigning the property to check whether the assigned argument is the Object's own property or not, the property 'polluted' will be directly be assigned to the new object thereby polluting the Object prototype. Using the example below, if there is a check to validate 'polluted' the valued later in the code, it would be substituted as "Yes! Its Polluted" as it had been polluted. PoC Code ```js var changeset = require("changeset") const patch = [{ type: 'put', key: ["__proto__", "polluted"], value: "Yes! Its Polluted" }]; console.log("Before : " + {}.polluted); changeset.apply(patch, {}, true); console.log("After : " + {}.polluted); ```