python-jinja2 : addresss CVE-2024-22195, CVE-2024-34064, CVE-2024-56201, CVE-2024-56326

[Kanishk-Bansal]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

Change Log

• CVE-2024-22195
• CVE-2024-34064
• CVE-2024-56201
• CVE-2024-56326

Does this affect the toolchain?

YES

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-22195
• https://nvd.nist.gov/vuln/detail/CVE-2024-34064
• https://nvd.nist.gov/vuln/detail/CVE-2024-56201
• https://nvd.nist.gov/vuln/detail/CVE-2024-56326

Test Methodology

• Pipeline build id: 704109
• P-tests of python-jinja2 are already failing, that's why in buddy build test section is failing.

[mbykhovtsev-ms]

Just FYI the p-tests that are failing have been failing for all the past. Their failure is not caused by the changes