Vulnerability in sylius/resource-bundle (CVE-2020-15143)
Summary
Vulnerability in sylius/resource-bundle (CVE-2020-15143). Data can be tampered with by attackers. Exploitable via addslashes. Mitigation: upgrade to 1.3.14 or later.
Original description
The description as published by the source.
Impact
Request parameters injected inside an expression evaluated by symfony/expression-language package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.
The vulnerable versions include: <=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3.
Example
foo:
path: /foo/{id}
defaults:
_sylius:
repository:
method: findSome
arguments:
entity: "expr:service('repository').find($id)"
In this case, $id can be prepared in a way that calls other services.
If you visit /foo/"~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~", it will result in a following expression expr:service('repository').find(""~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~""), which will execute a query on the currently connected database.
To find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.
Patches
This issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.
Workarounds
The fix requires adding addslashes in ParametersParser::parseRequestValueExpression to sanitize user input before evaluating it using the expression language.
- return is_string($v…
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-15143 has been found in sylius/resource-bundle.
Attackers can target a specific entry point like addslashes over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade sylius/resource-bundle to 1.3.14 or later.
If unsure, ask your IT team or search "sylius/resource-bundle CVE-2020-15143" on the vendor's site.
CVE-2020-15143 (sylius/resource-bundle) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Attack surface: addslashes
Patched: 1.3.14 — 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-74) exists in sylius/resource-bundle. Attackers reach the vulnerable code path via addslashes.
Check the vendor advisory for the affected versions of sylius/resource-bundle. Attack surface: addslashes.
Severity: ?. Data can be tampered with by attackers.
Update to 1.3.14.
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.14ステージング環境で 1.3.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com