[Snyk] Security upgrade numpy from 1.14.5 to 1.22.2

[shwetasah-cape]

This PR was automatically created by Snyk using the credentials of a real user.

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

tensorflow 1.13.1 requires grpcio, which is not installed.
tensorboard 1.13.1 requires grpcio, which is not installed.
Sphinx 1.8.6 has requirement docutils<0.18,>=0.11, but you have docutils 0.18.1.
pyasn1-modules 0.2.8 has requirement pyasn1<0.5.0,>=0.4.6, but you have pyasn1 0.4.2.
google-auth 1.35.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
google-api-core 1.32.0 has requirement protobuf<3.18.0,>=3.12.0; python_version < "3", but you have protobuf 3.6.1.
google-api-core 1.32.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	NULL Pointer Dereference SNYK-PYTHON-NUMPY-2321964	numpy: 1.14.5 -> 1.22.2	No	Proof of Concept
	399/1000 Why? Has a fix available, CVSS 3.7	Buffer Overflow SNYK-PYTHON-NUMPY-2321966	numpy: 1.14.5 -> 1.22.2	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Buffer Overflow SNYK-PYTHON-NUMPY-2321969	numpy: 1.14.5 -> 1.22.2	No	Proof of Concept
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-NUMPY-2321970	numpy: 1.14.5 -> 1.22.2	No	Proof of Concept
	811/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.8	Arbitrary Code Execution SNYK-PYTHON-NUMPY-73513	numpy: 1.14.5 -> 1.22.2	No	Proof of Concept

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

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Denial of Service (DoS)
🦉 Arbitrary Code Execution