Skip to content

[Snyk] Security upgrade opencv-python from 3.2.0.6 to 4.2.0.32 #14

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

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

Conversation

snyk-bot
Copy link

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
nbformat 4.4.0 requires jsonschema, which is not installed.
jupyter 1.0.0 requires qtconsole, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Buffer Overflow
SNYK-PYTHON-OPENCVPYTHON-1731320
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Out-of-bounds Read
SNYK-PYTHON-OPENCVPYTHON-1731324
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Out-of-bounds Read
SNYK-PYTHON-OPENCVPYTHON-1731332
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Division by zero
SNYK-PYTHON-OPENCVPYTHON-1731340
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-OPENCVPYTHON-1731342
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-OPENCVPYTHON-1731344
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-OPENCVPYTHON-1731346
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
medium severity 561/1000
Why? Recently disclosed, Has a fix available, CVSS 5.5
Improper Input Validation
SNYK-PYTHON-OPENCVPYTHON-1731348
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-OPENCVPYTHON-1731350
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Buffer Overflow
SNYK-PYTHON-OPENCVPYTHON-1731352
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-OPENCVPYTHON-1731354
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Write
SNYK-PYTHON-OPENCVPYTHON-1731356
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 696/1000
Why? Recently disclosed, Has a fix available, CVSS 8.2
Out-of-bounds Read
SNYK-PYTHON-OPENCVPYTHON-1731360
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Out-of-Bounds
SNYK-PYTHON-OPENCVPYTHON-1731364
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Read
SNYK-PYTHON-OPENCVPYTHON-1731366
opencv-python:
3.2.0.6 -> 4.2.0.32
No No Known Exploit
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Out-of-bounds Read
SNYK-PYTHON-OPENCVPYTHON-1731368
opencv-python:
3.2.0.6 -> 4.2.0.32
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

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.

1 participant