org.webjars.npm:dagre-d3-es@7.0.11 vulnerabilities

latest version

7.0.11

first published

2 years ago

latest version published

6 months ago

licenses detected

MIT
[7.0.8,)

package registry

View on Maven Central Repository

Go back to all versions of this package

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the org.webjars.npm:dagre-d3-es package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability Vulnerable Version

Vulnerability	Vulnerable Version
M Prototype Pollution org.webjars.npm:dagre-d3-es is a <a href="https://www.npmjs.com/dagre- Affected versions of this package are vulnerable to Prototype Pollution via the `addConflict` function in the `bk` module. An attacker can modify the JavaScript Object prototype chain by injecting malicious input values, which may result in denial of service, unexpected application behavior, or potential execution of arbitrary code when polluted properties are accessed or executed. Note: Project maintainers have stated that there is no known vector for this vulnerability in the package's code, though one may be opened by downstream implementations. The PoC has been validated as a theoretical vector, and a patch has been merged to address it. How to fix Prototype Pollution? A fix was pushed into the `master` branch but not yet published.	[0,)

Prototype Pollution

org.webjars.npm:dagre-d3-es is a

<a href="https://www.npmjs.com/dagre-

Affected versions of this package are vulnerable to Prototype Pollution via the addConflict function in the bk module. An attacker can modify the JavaScript Object prototype chain by injecting malicious input values, which may result in denial of service, unexpected application behavior, or potential execution of arbitrary code when polluted properties are accessed or executed.

Note: Project maintainers have stated that there is no known vector for this vulnerability in the package's code, though one may be opened by downstream implementations. The PoC has been validated as a theoretical vector, and a patch has been merged to address it.

How to fix Prototype Pollution?

A fix was pushed into the master branch but not yet published.

[0,)

Go back to all versions of this package