Vulnerability in webpack-subresource-integrity (CVE-2020-15262)
Summary
Vulnerability in webpack-subresource-integrity (CVE-2020-15262). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.1 or later.
Original description
The description as published by the source.
Impact
All dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected.
Patches
This issue is patched in version 1.5.1.
Workarounds
N/A
References
https://github.com/waysact/webpack-subresource-integrity/issues/131
For more information
If you have any questions or comments about this advisory:
- Comment on webpack-subresource-integrity issue #131
- Or email us at security@waysact.com
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-2020-15262 has been found in webpack-subresource-integrity.
Risk of unauthorized operations or information disclosure.
What to do: upgrade webpack-subresource-integrity to 1.5.1 or later.
If unsure, ask your IT team or search "webpack-subresource-integrity CVE-2020-15262" on the vendor's site.
CVE-2020-15262 (webpack-subresource-integrity) — CWE-345
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.5.1 — 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-345) exists in webpack-subresource-integrity.
Check the vendor advisory for the affected versions of webpack-subresource-integrity.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.1.
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 'webpack-subresource-integrity' . 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 'webpack-subresource-integrity' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
webpack-subresource-integrityを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade webpack-subresource-integrity to 1.5.1ステージング環境で 1.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com