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

[Snyk] Security upgrade PyYAML from 5.1.2 to 5.2 #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

xlogix
Copy link
Member

@xlogix xlogix commented Jan 29, 2021

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • requirements.txt
⚠️ Warning
thinc 7.0.8 requires cymem, which is not installed.
thinc 7.0.8 requires murmurhash, which is not installed.
thinc 7.0.8 requires srsly, which is not installed.
spacy 2.1.9 requires cymem, which is not installed.
spacy 2.1.9 requires murmurhash, which is not installed.
spacy 2.1.9 requires srsly, which is not installed.
preshed 2.0.1 requires cymem, which is not installed.
chatterbot-corpus 1.2.0 has requirement PyYAML<4.0,>=3.12, but you have PyYAML 5.4.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 876/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Improper Access Control
SNYK-PYTHON-PYYAML-550022
PyYAML:
5.1.2 -> 5.2
No Mature
high severity 704/1000
Why? Has a fix available, CVSS 9.8
Arbitrary Code Execution
SNYK-PYTHON-PYYAML-559098
PyYAML:
5.1.2 -> 5.2
No No Known Exploit
high severity 876/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Arbitrary Code Execution
SNYK-PYTHON-PYYAML-590151
PyYAML:
5.1.2 -> 5.2
No Mature

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants