[Snyk] Fix for 5 vulnerabilities

[spolti]

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:
  • docs/samples/v1beta1/triton/fastertransformer/transformer/requirements.txt

⚠️ Warning

ray 2.0.0 has requirement grpcio<=1.43.0,>=1.28.1; python_version < "3.10", but you have grpcio 1.59.0.
ray 2.0.0 has requirement protobuf<4.0.0,>=3.15.3, but you have protobuf 4.24.4.
kubernetes 28.1.0 has requirement urllib3<2.0,>=1.24.2, but you have urllib3 2.0.7.
kserve 0.10.2 has requirement avro>=1.11.0, but you have avro file-.avro-VERSION.txt.
kserve 0.10.2 has requirement numpy>=1.21.5, but you have numpy 1.21.3.
fastapi 0.88.0 has requirement starlette==0.22.0, but you have starlette 0.29.0.
botocore 1.31.68 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

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.21.3 -> 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.21.3 -> 1.22.2	No	No Known Exploit
	506/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-NUMPY-2321970	numpy: 1.21.3 -> 1.22.2	No	Proof of Concept
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-STARLETTE-3319937	starlette: 0.22.0 -> 0.27.0	No	No Known Exploit
	696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5	Directory Traversal SNYK-PYTHON-STARLETTE-5538332	starlette: 0.22.0 -> 0.27.0	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:

🦉 NULL Pointer Dereference
🦉 Denial of Service (DoS)
🦉 Directory Traversal