Vulnerability in sylius/resource-bundle (CVE-2020-5220)
Summary
Vulnerability in sylius/resource-bundle (CVE-2020-5220). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.3.13 or later.
Original description
The description as published by the source.
Sylius ResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API. Anyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: <1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=1.6.2. The patch is provided for Sylius ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.
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-5220 has been found in sylius/resource-bundle.
Risk of unauthorized operations or information disclosure.
What to do: upgrade sylius/resource-bundle to 1.3.13 or later.
If unsure, ask your IT team or search "sylius/resource-bundle CVE-2020-5220" on the vendor's site.
CVE-2020-5220 (sylius/resource-bundle) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.3.13 — 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-444) exists in sylius/resource-bundle.
Check the vendor advisory for the affected versions of sylius/resource-bundle.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.3.13.
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 'sylius/resource-bundle' . 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 'sylius/resource-bundle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sylius/resource-bundleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sylius/resource-bundle to 1.3.13ステージング環境で 1.3.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory nvd.nist.gov
- web github.com
- web github.com