cert-manager: Address CVE-2024-12401

[Ankita13-code]

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?
Address CVE-2024-12401 in the cert-manager package

Change Log

• Add patch for CVE-2024-12401 in cert-manager package

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-12401

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=706052&view=results (The buddy build is failing due to a known srpm issue)

[mbykhovtsev-ms]

The patch includes an addition of a binary file, however the build error suggests that you cannot include binary file changes as git diff patch. Unfortunately, that means that this cannot be patched like a regular patch and package upgrade is the only solution. I have checked and this patch is included in starting version 1.12.14. I think that is the only way to get this CVE patched for us.

[sameluch]

cert-manager has been upgraded to 1.12.15 recently. Does this CVE still apply with the upgrade? Is this PR still needed?
#12089

[mbykhovtsev-ms]

cert-manager has been upgraded to 1.12.15 recently. Does this CVE still apply with the upgrade? Is this PR still needed? #12089

No it should not be needed anymore as versions >= 1.12.14 include it

[jslobodzian]

This CVE is already fixed with the .15 version of cert-manager