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 pillow from 8.3.2 to 9.0.0 #4131

Merged
merged 1 commit into from
Jan 10, 2022

Conversation

snyk-bot
Copy link
Contributor

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:
    • cvat/requirements/base.txt
⚠️ Warning
sklearn 0.0 requires scikit-learn, which is not installed.
open3d 0.11.2 requires pandas, which is not installed.
nbconvert 6.4.0 has requirement mistune<2,>=0.8.1, but you have mistune 2.0.1.
datumaro 0.2 requires scipy, which is not installed.
datumaro 0.2 requires pandas, which is not installed.
datumaro 0.2 requires opencv-python, which is not installed.
azure-storage-blob 12.8.1 requires cryptography, which is not installed.
argon2-cffi 21.3.0 requires argon2-cffi-bindings, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
critical severity 776/1000
Why? Recently disclosed, Has a fix available, CVSS 9.8
Arbitrary Code Execution
SNYK-PYTHON-PILLOW-2331901
pillow:
8.3.2 -> 9.0.0
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Buffer Over-read
SNYK-PYTHON-PILLOW-2331905
pillow:
8.3.2 -> 9.0.0
No No Known Exploit
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Improper Initialization
SNYK-PYTHON-PILLOW-2331907
pillow:
8.3.2 -> 9.0.0
No No Known Exploit

(*) 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

@nmanovic nmanovic merged commit 4e65d77 into develop Jan 10, 2022
@nmanovic nmanovic deleted the snyk-fix-6df848b7f50b105cfe0be813964f83b2 branch January 10, 2022 08:17
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