Vulnerability in oro/platform (CVE-2021-43852)
Summary
Vulnerability in oro/platform (CVE-2021-43852). Risk of unauthorized operations or information disclosure. Exploitable via __proto__. Mitigation: upgrade to 4.2.8 or later.
Original description
The description as published by the source.
Summary
By sending a specially crafted request, an attacker could inject properties into existing JavaScript language construct prototypes, such as objects. Later this injection may lead to JS code execution by libraries that are vulnerable to Prototype Pollution.
Workarounds
Configure WAF to drop requests containing next strings: __proto__ , constructor[prototype], constructor.prototype
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-43852 has been found in oro/platform.
Attackers can target a specific entry point like __proto__ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade oro/platform to 4.2.8 or later.
If unsure, ask your IT team or search "oro/platform CVE-2021-43852" on the vendor's site.
CVE-2021-43852 (oro/platform) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: __proto__ / constructor.prototype
Patched: 4.2.8 — apply immediately
Workaround: Configure WAF to drop requests containing next strings: __proto__ , constructor[prototype], constructor.prototype
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-1321) exists in oro/platform. Attackers reach the vulnerable code path via __proto__ without authentication.
Check the vendor advisory for the affected versions of oro/platform. Attack surface: __proto__ / constructor.prototype.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.2.8.
Workaround: Configure WAF to drop requests containing next strings: __proto__ , constructor[prototype], constructor.prototype
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'oro/platform' . 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 'oro/platform' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
oro/platformを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Configure WAF to drop requests containing next strings: `__proto__` , `constructor[prototype]`, `constructor.prototype`パッチが適用されるまでの応急処置として、Configure WAF to drop requests containing next strings:
__proto__,constructor[prototype],constructor.prototypeを実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade oro/platform to 4.2.8ステージング環境で 4.2.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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