[Snyk] Security upgrade js-yaml from 4.1.1 to 4.3.1

[sestinj]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• extensions/cli/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18593780	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[sestinj]

This minor version upgrade for js-yaml introduces security enhancements and bug fixes. While not containing major API changes, one change introduces a new default that could affect specific use cases.

Key Changes:

• New maxDepth Loader Option: Version 4.2.0 introduced a maxDepth option to the loader, which defaults to 100. This is a security hardening measure to prevent Denial of Service (DoS) attacks caused by deeply nested YAML documents. [1]
• Security Fixes: The upgrade to 4.3.0 and higher resolves vulnerabilities related to inefficient algorithmic complexity in merge key (<<) handling, which could also lead to DoS. [5]

Potential Impact:

• The maxDepth default could cause errors in applications that legitimately process YAML files with a nesting depth greater than 100. Previously, these would have been parsed without error (though potentially causing performance issues).

Recommendation:
Verify if your application processes YAML documents with a nesting depth exceeding 100. If so, you may need to explicitly configure the maxDepth loader option to a higher value to avoid new errors.

Source: GitHub Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.