Vulnerability in @scandipwa/magento-scripts (CVE-2021-32684)
Summary
Vulnerability in @scandipwa/magento-scripts (CVE-2021-32684). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.3 or later.
Original description
The description as published by the source.
magento-scripts contains scripts and configuration used by Create Magento App, a zero-configuration tool-chain which allows one to deploy Magento 2. In versions 1.5.1 and 1.5.2, after changing the function from synchronous to asynchronous there wasn't implemented handler in the start, stop, exec, and logs commands, effectively making them unusable. Version 1.5.3 contains patches for the problems.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32684 has been found in @scandipwa/magento-scripts.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @scandipwa/magento-scripts to 1.5.3 or later.
If unsure, ask your IT team or search "@scandipwa/magento-scripts CVE-2021-32684" on the vendor's site.
CVE-2021-32684 (@scandipwa/magento-scripts) — CWE-670
Attack vector: local / no user interaction
Patched: 1.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-670) exists in @scandipwa/magento-scripts.
Check the vendor advisory for the affected versions of @scandipwa/magento-scripts.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@scandipwa/magento-scripts' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@scandipwa/magento-scripts' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@scandipwa/magento-scriptsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @scandipwa/magento-scripts to 1.5.3ステージング環境で 1.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- patch github.com
- patch github.com