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:
  • machine-learning/sift/requirements.txt

Vulnerabilities that will be fixed

By pinning:

Severity	Issue	Upgrade	Breaking Change	Exploit Maturity
	Buffer Overflow SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731318	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731322	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Write SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731326	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731330	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Division by Zero SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731338	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731358	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-Bounds SNYK-PYTHON-OPENCVCONTRIBPYTHON-1731362	opencv-contrib-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Buffer Overflow SNYK-PYTHON-OPENCVPYTHON-1731320	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVPYTHON-1731324	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Write SNYK-PYTHON-OPENCVPYTHON-1731328	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVPYTHON-1731332	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Division by Zero SNYK-PYTHON-OPENCVPYTHON-1731340	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-bounds Read SNYK-PYTHON-OPENCVPYTHON-1731360	opencv-python: 3.4.2.16 -> 4.2.0.32	No	No Known Exploit
	Out-of-Bounds SNYK-PYTHON-OPENCVPYTHON-1731364	opencv-python: 3.4.2.16 -> 4.2.0.32	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