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

Current axios version contains CSRF vulnerability. #3369

Closed
1 task done
iSpyte opened this issue May 4, 2024 · 1 comment
Closed
1 task done

Current axios version contains CSRF vulnerability. #3369

iSpyte opened this issue May 4, 2024 · 1 comment
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f

Comments

@iSpyte
Copy link

iSpyte commented May 4, 2024

  • The FAQ doesn't contain a resolution to my issue

Versions

  • mineflayer: <= 4.20.1
  • server: vanilla/spigot/paper Any
  • node: 20.12.2 (but I haven't tested any other versions)

Detailed description of a problem

Wanted to get this out as I haven't seen any issue posts about this recently.

When installing mineflayer using npm, npm states that it found 5 vulnerabilities after install. Upon entering npm audit it appears that the current version of the library Axios contains a Cross-Site Request Forgery vulnerability which is detailed in the links below. I should note it has now been patched in any version beyond 1.6.0. Current Axios version used by mineflayer is 0.21.4.

Github advisory:
GHSA-wf5p-g6vw-rhxx

Axios issue post
axios/axios#6022

CSRF Definition:
https://owasp.org/www-community/attacks/csrf

Additional context

The versions of axios affected are any below 1.6.0. Also using npm audit fix with or without --force doesn't fix the issue.

8wn7UmBgQz

Code_B5dSNjdhfX

@iSpyte iSpyte added possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f labels May 4, 2024
@extremeheat
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f
Projects
None yet
Development

No branches or pull requests

2 participants