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 django from 3.2.11 to 3.2.12 #4275

Merged
merged 1 commit into from
Feb 2, 2022

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Feb 2, 2022

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
tensorboardX 2.4.1 requires numpy, which is not installed.
sklearn 0.0 requires scikit-learn, which is not installed.
plyfile 0.7.4 requires numpy, which is not installed.
open3d 0.11.2 requires pandas, which is not installed.
open3d 0.11.2 requires numpy, which is not installed.
nbconvert 6.4.1 has requirement mistune<2,>=0.8.1, but you have mistune 2.0.2.
matplotlib 3.5.1 requires numpy, which is not installed.
h5py 2.10.0 requires numpy, which is not installed.
google-api-core 2.4.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
datumaro 0.2 requires numpy, which is not installed.
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.
datumaro 0.2 requires pycocotools, 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 Issue Upgrade Breaking Change Exploit Maturity
medium severity Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002
django:
3.2.11 -> 3.2.12
No No Known Exploit
medium severity Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021
django:
3.2.11 -> 3.2.12
No No Known Exploit

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

@snyk-bot snyk-bot requested a review from nmanovic as a code owner February 2, 2022 09:02
@nmanovic nmanovic merged commit 61787ce into develop Feb 2, 2022
@nmanovic nmanovic deleted the snyk-fix-acdc2e7fa2a8c6053c3cdf6d93834db4 branch February 2, 2022 13:33
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