| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| lodash | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash-amd | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash-es | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash.template | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash-amd | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash-es | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
| lodash.template | ≥ 4.0.0, < 4.18.0 | 4.18.0 |
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. 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().
Users should upgrade to version 4.18.0.
The fix applies two changes:
importsKeys against the existing reForbiddenIdentifierChars regex (same check already used for the variable option)assignInWith with assignWith when merging imports, so only own properties are enumeratedDo not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン