-
-
Notifications
You must be signed in to change notification settings - Fork 886
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
CVE-2021-44906 vulnerability in uri-js dependency #1978
Comments
@zekth have you had any problems with your replacement, that is now possible to use via options? Do you think it would be ok to switch to it in v9 completely? It's probably worth putting a comment somewhere that the default option has this vulnerability, and it is best to use another URI library in scenarios that may be affected (specifically, untrusted schemas). |
I had no bug feedback on this, we're using fast-uri by default in fastify v4. @mcollina could you confirm we don't have any issue since we merged it by default? |
We had no issues with fast-uri so far. We should also investigate why minimist is in there and where it is used. |
Is it perhaps good enough to use the built-in URL module of nodejs now? |
It does not provide the required featureset |
Another reason to leave |
The CVE-2021-44906 vulnerability is found in stale
uri-js
dependency. garycourt/uri-js#72The version of Ajv you are using
8.11.0
Operating system and node.js version
macos
16.15.0
Package manager and its version
npm 8.9.0
Link to (or contents of) package.json
Error messages
none
The output of
npm ls
├── @babel/[email protected]
├── @babel/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]
The text was updated successfully, but these errors were encountered: