Vulnerability in openmage/magento-lts (CVE-2020-15151)
Summary
Vulnerability in openmage/magento-lts (CVE-2020-15151). Confidential information can be exposed externally. Mitigation: upgrade to 20.0.2 or later.
Original description
The description as published by the source.
OpenMage LTS before versions 19.4.6 and 20.0.2 allows attackers to circumvent the fromkey protection in the Admin Interface and increases the attack surface for Cross Site Request Forgery attacks. This issue is related to Adobe's CVE-2020-9690. It is patched in versions 19.4.6 and 20.0.2.
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-15151 has been found in openmage/magento-lts.
Confidential information can be exposed externally.
What to do: upgrade openmage/magento-lts to 20.0.2 or later.
If unsure, ask your IT team or search "openmage/magento-lts CVE-2020-15151" on the vendor's site.
CVE-2020-15151 (openmage/magento-lts) — CWE-203
Attack vector: remote (network-reachable) / unauthenticated
Patched: 20.0.2 — 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-203) exists in openmage/magento-lts.
Check the vendor advisory for the affected versions of openmage/magento-lts.
Severity: ?. Confidential information can be exposed externally.
Update to 20.0.2.
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 'openmage/magento-lts' . 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 'openmage/magento-lts' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openmage/magento-ltsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openmage/magento-lts to 20.0.2ステージング環境で 20.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory helpx.adobe.com
- package github.com
- web nvd.nist.gov