-
Notifications
You must be signed in to change notification settings - Fork 16
Upgrading upstream dep to avoid vulnerability #32
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Our Bot Framework samples have a nested dependency on prim. Looking forward to upgrading to the prim version that carries this json-schema v 0.4.0 dependency, thereby fixing the vulnerability. Any ETA on when the patch will be available?
|
@bahamat any feedback on this? |
| "assert-plus": "^1.0.0", | ||
| "extsprintf": "^1.3.0", | ||
| "json-schema": "^0.4.0", | ||
| "verror": "^1.10.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you adding carets? If you think this is a good idea, you should separate this into a different PR, otherwise you risk that this PR will get lost in discussion due to that unexpected change. Or was that merely by mistake?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it from the previous PR.
|
Fixed in 017f744 |
Prototype polution: https://security.snyk.io/vuln/SNYK-JS-JSONSCHEMA-1920922
Incorporates #27 since it's got a better representation for the remaining deps.