critical

CVE-2020-15256

object-path: Prototype pollution could result in DoS or RCE

Published 19 Oct 2020Modified 17 Jun 2026CWE 20, 471

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

GHSA7.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H

Red Hat9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by GHSA (high), Red Hat (high), Ubuntu (low).

Description

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. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.

Affected packages and fixed versions

Source	Package	Fixed in
debian 10	node-object-path	0.11.4-2+deb10u1
debian 11	node-object-path	0.11.5-3
debian 12	node-object-path	0.11.5-3
debian 13	node-object-path	0.11.5-3
debian 14	node-object-path	0.11.5-3
debian 9	node-object-path	no fix listed
echo	node-object-path	0.11.5-3
npm::GitHub Security Advisory npm	object-path	0.11.5
ubuntu 18.04	node-object-path	0.11.3-1ubuntu0.1
ubuntu 18.04-ESM	node-object-path	0.11.3-1ubuntu0.1
ubuntu 20.04	node-object-path	0.11.4-2ubuntu0.1
ubuntu 20.04-ESM	node-object-path	0.11.4-2ubuntu0.1

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs