fix(appsec): bump @datadog/wasm-js-rewriter to 5.0.2 to resolve js-yaml vulnerability (GHSA-5p4m-2wfm-xmqj) #9768
+13
−10
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -295,12 +295,12 @@ | |
| pprof-format "^2.2.1" | ||
| source-map "^0.8.0" | ||
|
|
||
| "@datadog/wasm-js-rewriter@5.0.2": | ||
| version "5.0.2" | ||
| resolved "https://registry.yarnpkg.com/@datadog/wasm-js-rewriter/-/wasm-js-rewriter-5.0.2.tgz#f7cb491d02a0ce54429ca732f3dba5436b5e9271" | ||
| integrity sha512-ffv9TqdtuE8XnZgaGnmMIU1A+t+eaHIEbdVpV5elijq1dKK03OqFb+Xo4ojTbgCwxIYDA1zmA8TnZJBjtzuVuw== | ||
| dependencies: | ||
| js-yaml "^4.1.1" | ||
|
There was a problem hiding this comment.
Fresh evidence after the added resolution: this new Useful? React with 👍 / 👎. |
||
| lru-cache "^7.14.0" | ||
| module-details-from-path "^1.0.3" | ||
| node-gyp-build "^4.5.0" | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still depends on
js-yamlthrough^4.1.1, and the checked-in lockfile continues to resolve the combinedjs-yaml@^4.1.0, js-yaml@^4.1.1entry to4.1.1. GHSA-5p4m-2wfm-xmqj marks>=4.0.0 <4.3.1as affected and4.3.1as patched, so repo installs and lockfile-based consumers remain vulnerable even after this bump; please use a rewriter release/override that requiresjs-yaml >=4.3.1 <5and update the lockfile accordingly.Useful? React with 👍 / 👎.