ΠΠΏΠΈΡΠ°Π½ΠΈΠ΅
The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only developer-controlled, static key names.
| Π Π΅Π»ΠΈΠ· | Π‘ΡΠ°ΡΡΡ | ΠΡΠΈΠΌΠ΅ΡΠ°Π½ΠΈΠ΅ |
|---|---|---|
| devel | not-affected | 4.18.1+dfsg1-2 |
| esm-apps-legacy/xenial | released | 2.4.1+dfsg-3ubuntu0.1~esm1 |
| esm-apps/bionic | released | 4.17.4+dfsg-1ubuntu0.1~esm1 |
| esm-apps/focal | released | 4.17.15+dfsg-2ubuntu0.1~esm1 |
| esm-apps/jammy | released | 4.17.21+dfsg+~cs8.31.198.20210220-5ubuntu0.1~esm1 |
| esm-apps/noble | released | 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.24.04.1~esm1 |
| esm-apps/resolute | released | 4.17.23+dfsg-1ubuntu0.1~esm1 |
| esm-apps/xenial | ignored | end of ESM support, was needs-triage |
| jammy | needed | 4.17.21+dfsg+~cs8.31.198.20210220-5 |
| noble | needed | 4.17.21+dfsg+~cs8.31.198.20210220-9 |
ΠΠΎΠΊΠ°Π·ΡΠ²Π°ΡΡ ΠΏΠΎ
Π‘ΡΡΠ»ΠΊΠΈ Π½Π° ΠΈΡΡΠΎΡΠ½ΠΈΠΊΠΈ
EPSS
9.8 Critical
CVSS3
Π‘Π²ΡΠ·Π°Π½Π½ΡΠ΅ ΡΡΠ·Π²ΠΈΠΌΠΎΡΡΠΈ
Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only developer-controlled, static key names.
The fix for CVE-2021-23337 added validation for the variable option in ...
lodash vulnerable to Code Injection via `_.template` imports key names
ELSA-2026-19167: pcs security update (IMPORTANT)
EPSS
9.8 Critical
CVSS3