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

Solve security vulnerabilities #878

Closed
vpetersson opened this issue Aug 15, 2018 · 2 comments
Closed

Solve security vulnerabilities #878

vpetersson opened this issue Aug 15, 2018 · 2 comments
Labels
Milestone

Comments

@vpetersson
Copy link
Contributor

Snyk reported a number of vulnerabilities. We should update and patch them.

screen shot 2018-08-15 at 2 16 15 pm

screen shot 2018-08-15 at 2 16 10 pm

screen shot 2018-08-15 at 2 16 03 pm

screen shot 2018-08-15 at 2 15 59 pm

@umeboshi2
Copy link
Contributor

Ansible has been using only yaml.safe_load() since v1.1. The suggested fix in PyYaml is to rename .load() to dangerous_load() and defaulting to safe_load behavior on the .load() function. This should be fixed in pyyaml 4.2. Until then, since only ansible seems to be using it, and it uses it safely, this shouldn't be a problem for screenly. (yaml/pyyaml#207)

https://github.com/ansible/ansible/blob/stable-2.5/changelogs/CHANGELOG-legacy.rst#11-mean-street----422013

@stale
Copy link

stale bot commented Nov 2, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 2, 2018
@stale stale bot closed this as completed Nov 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants