CVE-2021-25915: Changeset Changeset Vulnerable To Prototype Pollution Vulnerability

CRITICAL
Advisory Identifier: GHSA-2gqw-q9r9-7f79
Share
CVSS 9.8
CWE-1321
Published
Advisory Summary

CVE-2021-25915 is a CRITICAL (CVSS 9.8) changeset vulnerable to prototype pollution vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting Changeset libraries in the npm ecosystem. The issue involves changeset vulnerable to prototype pollution. Remediation is available by upgrading affected packages to version 0.2.5.

CVE-2021-25915 at a Glance

CVE Identifier CVE-2021-25915
GHSA Identifier GHSA-2gqw-q9r9-7f79
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product Changeset
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2021-25915

To remediate this vulnerability, upgrade all affected Changeset dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

changeset fixed: 0.2.5 
npm install changeset@0.2.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls changeset

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2021-25915, inspect your project dependencies using npm:

npm ls changeset

Analyze the terminal output to locate any version of Changeset in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.5), your application is affected.

Note: The npm ls changeset command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where the product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. In Changeset, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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); ```

CVE-2021-25915 Affected Changeset Versions

1 component(s)
Fixed Versions:
0.2.5
Product / Package Ecosystem Affected Versions Fixed Version
changeset
npm/changeset
npm
≥ 0.0.1
< 0.2.5
0.2.5

References

NVD — CVE-2021-25915 NVD
https://nvd.nist.gov/vuln/detail/CVE-2021-25915
Security Fix Commit FIX COMMIT
https://github.com/eugeneware/changeset/commit/9e588844edbb9993b32e7366cc799262b4447f99
Changeset Source Repository REPOSITORY
https://github.com/eugeneware/changeset
web.archive.org/web/20210323102946/... WEB
https://web.archive.org/web/20210323102946/https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25915

Frequently Asked Questions

What is CVE-2021-25915?
CVE-2021-25915 is a security vulnerability in Changeset involving Changeset vulnerable to prototype pollution under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which Changeset versions are affected?
Affected versions include releases prior to 0.2.5 across affected packages: changeset.
What version fixes CVE-2021-25915?
Upgrading to 0.2.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is changeset affected?
Yes, changeset is affected in releases prior to 0.2.5. Upgrade your dependency to 0.2.5 or later.
What is the CVSS score of CVE-2021-25915?
CVE-2021-25915 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2021-25915?
CVE-2021-25915 is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.).
How can I check npm dependencies for CVE-2021-25915?
Run the dependency tree command: 'npm ls changeset'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2gqw-q9r9-7f79",
  "modified" : "2023-10-19T18:27:41Z",
  "published" : "2022-05-24T17:44:00Z",
  "aliases" : [ "CVE-2021-25915" ],
  "summary" : "Changeset vulnerable to prototype pollution",
  "details" : "### Overview\nPrototype 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.\n\n### Details\nThe 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.\n\n### PoC Details\nThe '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.\n\n### PoC Code\n\n```js\nvar changeset = require(\"changeset\") const patch = [{\n    type: 'put',\n    key: [\"__proto__\", \"polluted\"],\n    value: \"Yes! Its Polluted\"\n}];\nconsole.log(\"Before : \" + {}.polluted);\nchangeset.apply(patch, {}, true);\nconsole.log(\"After : \" + {}.polluted);\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "changeset"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.1"
      }, {
        "fixed" : "0.2.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-25915"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eugeneware/changeset/commit/9e588844edbb9993b32e7366cc799262b4447f99"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eugeneware/changeset"
  }, {
    "type" : "WEB",
    "url" : "https://web.archive.org/web/20210323102946/https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25915"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-10-19T18:27:41Z",
    "nvd_published_at" : "2021-03-09T15:15:00Z"
  }
}