-
Notifications
You must be signed in to change notification settings - Fork 601
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
update lodash@^4.17.21:, dns-packet@^1.34: through dependencies resol… #4783
update lodash@^4.17.21:, dns-packet@^1.34: through dependencies resol… #4783
Conversation
Added @radium-v as a reviewer. I defer my "required" review to him. |
@Ibrahimmaga what is your testing process and how did you go about testing? |
The testing is done locally by running yarn after the update. The dependencies are also validated when running the pipeline on clean servers. An update through resolution means we will have both old versions and the new version on yarn.lock so things don't break because of the new update. |
this can also do the trick. Co-authored-by: John Kreitlow <[email protected]>
I would also get in the habit of running each script in the package.json file that's being updated to ensure there are no unforeseen breakages. |
@Ibrahimmaga can you regenerate the lockfile and update the PR title now that |
Pull Request
📖 Description
CVE-2021-23386
high severity
Vulnerable versions: < 5.2.2
Patched version: 5.2.2
This affects the package dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
CVE-2021-23337
high severity
Vulnerable versions: < 4.17.21
Patched version: 4.17.21
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
🎫 Issues
👩💻 Reviewer Notes
📑 Test Plan
✅ Checklist
General
$ yarn change
Component-specific
⏭ Next Steps