Vulnerability in object-path (CVE-2020-15256)
Summary
Vulnerability in object-path (CVE-2020-15256). Data can be tampered with by attackers. Exploitable via includeInheritedProps. Mitigation: upgrade to 0.11.5 or later.
Original description
The description as published by the source.
Impact
A prototype pollution vulnerability has been found in object-path <= 0.11.4 affecting the set() method. The vulnerability is limited to the includeInheritedProps mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of object-path and setting the option includeInheritedProps: true, or by using the default withInheritedProps instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of set() in versions < 0.11.0 is vulnerable.
Patches
Upgrade to version >= 0.11.5
Workarounds
Don't use the includeInheritedProps: true options or the withInheritedProps instance if using a version >= 0.11.0.
References
Read more about the prototype pollution vulnerability
For more information
If you have any questions or comments about this advisory:
- Open an issue in object-path
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-15256 has been found in object-path.
Attackers can target a specific entry point like includeInheritedProps over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade object-path to 0.11.5 or later.
If unsure, ask your IT team or search "object-path CVE-2020-15256" on the vendor's site.
CVE-2020-15256 (object-path) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: includeInheritedProps / withInheritedProps
Patched: 0.11.5 — apply immediately
Workaround: Don't use the includeInheritedProps: true options or the withInheritedProps instance if using a version >= 0.11.0.
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-20) exists in object-path. Attackers reach the vulnerable code path via includeInheritedProps without authentication.
Check the vendor advisory for the affected versions of object-path. Attack surface: includeInheritedProps / withInheritedProps.
Severity: ?. Data can be tampered with by attackers.
Update to 0.11.5.
Workaround: Don't use the includeInheritedProps: true options or the withInheritedProps instance if using a version >= 0.11.0.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'object-path' . 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 'object-path' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
object-pathを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.パッチが適用されるまでの応急処置として、Don't use the
includeInheritedProps: trueoptions or thewithInheritedPropsinstance if using a version >= 0.11.0. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade object-path to 0.11.5ステージング環境で 0.11.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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