-
-
Notifications
You must be signed in to change notification settings - Fork 169
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 [email protected] to 1.0.9 #252
Comments
+1 |
Merged into master. What is the effect of the |
A vulnerability was found in which a specially formed payload sent over a web socket could gain access to updating docs in the DB. https://forums.meteor.com/t/meteor-allow-deny-vulnerability-disclosure/39500 |
@alanning Will you update the Atmosphere package to reflect what is currently on master? |
I am aware of the vulnerability. The Roles package itself does not use allow/deny directly so it is not directly vulnerable to my knowledge. I am wondering if I need to update the Atmosphere package. Not sure what effect, if any, having the older version in But this is all conjecture which is why I was asking to see if anyone had more concrete knowledge about this. |
I am also unsure here if anything should be done. It is a patch bump. Anyone can just update it locally in their app. This package is not preventing that in any way. |
I think this has been done. |
Following the Meteor Allow-Deny Vulnerability Disclosure, the dependency to
allow-deny
in fileroles/.versions
should be updated to1.0.9
to fix it.The text was updated successfully, but these errors were encountered: