lodash vulnerable to Code Injection via `_.template` imports key names
lodash · lodash-es · lodash-amd · lodash.template
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| lodash npm |
|
|
| lodash-es npm |
|
|
| lodash-amd npm |
lodash · lodash-es · lodash-amd · lodash.template
| Product | Affected | Fixed in |
|---|---|---|
| lodash npm |
|
|
| lodash-es npm |
|
|
| lodash-amd npm |
≥ 4.0.0 · < 4.18.0
|
| lodash.template npm |
|
|
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.
From the CVE record · openjs
lodash, lodash-es, lodash-amd, and lodash.template are vulnerable when an application passes untrusted key names in _.template’s options.imports. An attacker can execute arbitrary code during template compilation; keys inherited from a polluted Object.prototype can also reach the vulnerable code path. The input does not specify whether authentication, network access, or user interaction is required.
Check applications using npm lodash, lodash-es, lodash-amd, or lodash.template versions >=4.0.0 and <4.18.0; the input gives conflicting fixed versions.