org.webjars.npm:js-yaml@4.3.1

latest version

4.3.1

first published

11 years ago

latest version published

3 days ago

licenses detected

MIT
[2.0.5,)

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:js-yaml 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
H Inefficient Algorithmic Complexity org.webjars.npm:js-yaml is a human-friendly data serialization language. Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in the `readFlowCollection` function of `parser.ts`, which reaches exponential time when a flow sequence entry turns out to be a `key: value` pair and the parser rewinds to parse that entry a second time as the key. An attacker can exhaust CPU and block the Node event loop by supplying a small YAML document, under 200 bytes, with deeply nested flow sequences of `key: value` entries, since the re-parsing makes the work grow as O(2^n) in nesting depth. Exploitation occurs under the default configuration when the application parses untrusted YAML with `load()` or `loadAll()`, and needs no special schema, anchors, aliases, or merge keys. How to fix Inefficient Algorithmic Complexity? A fix was pushed into the `master` branch but not yet published.	[0,)

Inefficient Algorithmic Complexity

org.webjars.npm:js-yaml is a human-friendly data serialization language.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in the readFlowCollection function of parser.ts, which reaches exponential time when a flow sequence entry turns out to be a key: value pair and the parser rewinds to parse that entry a second time as the key. An attacker can exhaust CPU and block the Node event loop by supplying a small YAML document, under 200 bytes, with deeply nested flow sequences of key: value entries, since the re-parsing makes the work grow as O(2^n) in nesting depth. Exploitation occurs under the default configuration when the application parses untrusted YAML with load() or loadAll(), and needs no special schema, anchors, aliases, or merge keys.

How to fix Inefficient Algorithmic Complexity?

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

[0,)

Go back to all versions of this package