-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(security)(RCE) Upgrade jsonpath-plus to @^10.0.0 #4770
Comments
We're using pnpm and adding the following to package.json at least bumped the dependency for us, a quick ephemeral deployment shows tracing is still working however it's hard to say there aren't side-effects from this, so I would tread carefully if you're pushing this out to production. (especially ahead of the weekend)
|
For searching purposes, this relates to CVE-2024-21534 |
Fixes #4770 Co-authored-by: Juan Carlos Blanco Delgado <36451129+juancarlosjr97@users.noreply.github.com>
overriding is fine but could we get a bumped version of |
https://security.snyk.io/vuln/SNYK-JS-JSONPATHPLUS-7945884 The vulnerability was finally not solved by the latest version of @watson i'll allow myself to ping you, you're the one who closed the issue, should it maybe be re-opened with the goal of finding a workaround to the use of this lib ? tbh i have no clue of the impact it has on idk either if here's the issue JSONPath-Plus/JSONPath#226 on |
@adrsimon it has been fixed on v10.0.1 of |
From the dev that shipped the |
Fixes #4770 Co-authored-by: Juan Carlos Blanco Delgado <36451129+juancarlosjr97@users.noreply.github.com>
I see there's a copy/paste file from jsonpath-plus here: That should be unimpacted by this change because it's from version 10, right? Does |
Hello,
Snyk reported a security issue in one of my repos, because of one of the dependencies used by
dd-trace-js
.You can find the report here : https://security.snyk.io/vuln/SNYK-JS-JSONPATHPLUS-7945884
dd-trace-js
usesjsonpath-plus@^9.0.0
which contains a RCE.The only thing to do is upgrade the lib.
Thanks !
The text was updated successfully, but these errors were encountered: