Nodeca js-yaml
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in applications that parse untrusted YAML, and merge processing is enabled by default on these release lines. In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions 3.15.2, 4.3.2, and 5.4.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.0.0, < 3.15.2
- >= 4.0.0, < 4.3.2
- >= 5.0.0, < 5.4.1
Fixed in 3.15.2, 4.3.2, 5.4.1
Mitigation
Upgrade js-yaml to 3.15.2 or 4.3.2 or 5.4.1 or later.
References
- Vendor advisory github.com/nodeca/js-yaml/security/advisories/…
- Patch github.com/nodeca/js-yaml/pull/797
- Patch github.com/nodeca/js-yaml/commit/3485bc06ff8a0…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.