Versions of js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service. Reference: https://www.npmjs.com/package/js-yaml
External References: https://www.npmjs.com/advisories/788
Created nodejs-js-yaml tracking bugs for this issue: Affects: fedora-all [bug 1696232]
Created nodejs-js-yaml tracking bugs for this issue: Affects: epel-all [bug 1696233]
Upstream Patches: https://github.com/nodeca/js-yaml/commit/a567ef3c https://github.com/nodeca/js-yaml/commit/f64c6737
Created python-XStatic-JS-Yaml tracking bugs for this issue: Affects: openstack-rdo [bug 1719068]
This vulnerability is out of security support scope for the following product: * Red Hat Mobile Application Platform Please refer to https://access.redhat.com/support/policy/updates/rhmap for more details
This does not seem to be a vulnerability in the js-yaml package but rather it can result in a vulnerability if the load() method is used on untrusted input rather than safeLoad(). Any CVE assignments should be made to codebases using this package in an unsafe way, rather than the js-yaml package itself.