Skip to content
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 issue in axios dependency #759

Closed
tiltingpenguin opened this issue Aug 21, 2024 · 5 comments · Fixed by #760
Closed

Security issue in axios dependency #759

tiltingpenguin opened this issue Aug 21, 2024 · 5 comments · Fixed by #760

Comments

@tiltingpenguin
Copy link
Contributor

There was a SSRF security vulnerability found in axios (CVE-2024-39338), could you bump the version of axios used to 1.7.4 which is the patched version?

references:

@krassowski
Copy link
Member

@tiltingpenguin can you point to a place in code where axios is used?

@tiltingpenguin
Copy link
Contributor Author

axios is a dependency of a dependency ( nx ), but the vulnerable version is pulled in as you can see in the package-lock.json in line 6869. I can't say exactly if vulnerable code is used by nbdime as I haven't looked into it that deeply, but is there a reason to not update it?

@krassowski
Copy link
Member

krassowski commented Aug 21, 2024

Feel welcome to update it! This was just to highlight that axios is likely NOT used in the code shipped by nbdime (nor is nx).

See also jupyterlab/jupyterlab#16698

@tiltingpenguin
Copy link
Contributor Author

Thanks for making me aware of this. We got a bug in openSUSE Tumbleweed about the security issue, so I will update it just to be safe. But it would be great if you could provide a list of packages that are actually shipped in the future like in the jupyterlab issue you linked.

@krassowski
Copy link
Member

Thanks for the context and sorry for brevity.

But it would be great if you could provide a list of packages that are actually shipped in the future like in the jupyterlab issue you linked

Great to hear it would be useful! I wonder how we can make this easier for everyone. I know that GitHub recognised this problem with dependabot by allowing to auto-dismiss likely false positives (e.g. from packages only used in devDependencies): https://github.blog/changelog/2023-05-02-dependabot-alerts-now-automatically-dismiss-false-positives-for-npm-public-beta/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants