Bump js-yaml from 3.14.1 to 3.14.2 in /web-app in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the /web-app directory: js-yaml.

Updates js-yaml from 3.14.1 to 3.14.2

Changelog

Sourced from js-yaml's changelog.

[3.14.2] - 2025-11-15

Security

• Backported v4.1.1 fix to v3

[4.1.1] - 2025-11-12

Security

• Fix prototype pollution issue in yaml merge (<<) operator.

[4.1.0] - 2021-04-15

Added

• Types are now exported as yaml.types.XXX.
• Every type now has options property with original arguments kept as they were (see yaml.types.int.options as an example).

Changed

• Schema.extend() now keeps old type order in case of conflicts (e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as abcd instead of cbad).

[4.0.0] - 2021-01-03

Changed

• Check migration guide to see details for all breaking changes.
• Breaking: "unsafe" tags !!js/function, !!js/regexp, !!js/undefined are moved to js-yaml-js-types package.
• Breaking: removed safe* functions. Use load, loadAll, dump instead which are all now safe by default.
• yaml.DEFAULT_SAFE_SCHEMA and yaml.DEFAULT_FULL_SCHEMA are removed, use yaml.DEFAULT_SCHEMA instead.
• yaml.Schema.create(schema, tags) is removed, use schema.extend(tags) instead.
• !!binary now always mapped to Uint8Array on load.
• Reduced nesting of /lib folder.
• Parse numbers according to YAML 1.2 instead of YAML 1.1 (01234 is now decimal, 0o1234 is octal, 1:23 is parsed as string instead of base60).
• dump() no longer quotes :, [, ], (, ) except when necessary, #470, #557.
• Line and column in exceptions are now formatted as (X:Y) instead of at line X, column Y (also present in compact format), #332.
• Code snippet created in exceptions now contains multiple lines with line numbers.
• dump() now serializes undefined as null in collections and removes keys with undefined in mappings, #571.
• dump() with skipInvalid=true now serializes invalid items in collections as null.
• Custom tags starting with ! are now dumped as !tag instead of !<!tag>, #576.
• Custom tags starting with tag:yaml.org,2002: are now shorthanded using !!, #258.

Added

• Added .mjs (es modules) support.
• Added quotingType and forceQuotes options for dumper to configure string literal style, #290, #529.
• Added styles: { '!!null': 'empty' } option for dumper (serializes { foo: null } as "foo: "), #570.

... (truncated)

Commits

• 9963d36 3.14.2 released
• 10d3c8e dist rebuild
• 5278870 fix prototype pollution in merge (<<) (#731)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[fossabot]

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fossabot]

✓ Safe to upgrade

I recommend merging this upgrade because it patches a high-severity prototype pollution vulnerability in js-yaml without introducing breaking changes. The package is only present as a transitive dependency through react-scripts and is not directly imported or used in any application source code. The upgrade from version 3.14.1 to 3.14.2 is a patch-level security fix that adds protection against proto key manipulation during YAML parsing, with 2 bug fixes included.

What we checked

• js-yaml upgraded from 3.14.1 to 3.14.2 as a transitive dependency ^[1]
• js-yaml is pulled in through react-scripts 5.0.1 build tooling, not directly declared as a dependency ^[2]
• High-severity prototype pollution vulnerability (CVE) fixed in 3.14.2 by adding protection against proto key manipulation ^[3]

Dependency Usage

The js-yaml package is declared as a dependency resolution override in the web application but is not directly imported or used in any source code. This transitive dependency is pulled in by underlying build tools or testing frameworks (likely react-scripts or related packages) and is being pinned for security purposes to ensure YAML configuration files in the build pipeline are parsed safely, though the application itself does not process YAML data at runtime.

Changes

This update patches a critical prototype pollution vulnerability in js-yaml by implementing safe property assignment during YAML parsing, specifically preventing manipulation of the __proto__ key through a new setProperty() helper function that uses Object.defineProperty() for protection.

• Fixed prototype pollution vulnerability by adding protection against proto key manipulation in YAML parsing (CVE reference: Object properties should be created using defineProperty nodeca/js-yaml#164) (v3.14.2, other)
• Backported v4.1.1 fix to v3 (v3.14.2, changelog)
• Added setProperty() helper function to safely set object properties during YAML parsing, using Object.defineProperty() for proto key to prevent prototype pollution attacks (v3.14.2, other)

References (3)

[1]: js-yaml upgraded from 3.14.1 to 3.14.2 as a transitive dependency

console/web-app/yarn.lock

Line 11420 in 3b43178

resolution: "js-yaml@npm:3.14.2"

[2]: js-yaml is pulled in through react-scripts 5.0.1 build tooling, not directly declared as a dependency

console/web-app/package.json

Line 88 in 3b43178

"react-scripts": "5.0.1",

[3]: High-severity prototype pollution vulnerability (CVE) fixed in 3.14.2 by adding protection against proto key manipulation (source link)

---

fossabot analyzed this PR using dependency research. View this analysis on the web