fix(deps): update module github.com/cert-manager/cert-manager to v1.15.4 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/cert-manager/cert-manager	v1.15.3 → v1.15.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

cert-manager ha a potential slowdown / DoS when parsing specially crafted PEM inputs

GHSA-r4pg-vg54-wxx4

More information

Details

Impact

cert-manager packages which call the standard library pem.Decode() function can take a long time to process specially crafted invalid PEM data.

If an attacker is able to modify PEM data which cert-manager reads (e.g. in a Secret resource), they may be able to use large amounts of CPU in the cert-manager controller pod to effectively create a denial-of-service (DoS) vector for cert-manager in the cluster.

Secrets are limited in size to 1MiB, which reduces the impact of this issue; it was discovered through an ~856kB fuzz test input which causes pem.Decode to take roughly 750ms to reject the input on an M2 Max Macbook Pro. By way of comparison, a valid PEM-encoded 4096-bit RSA key takes roughly 70µs to parse on the same machine.

Given the required size of PEM data needed to present a realistic DoS vector, an attacker would need to create or insert many different large sized resources in the cluster, and so the best secondary defense is to ensure that sensible limits are placed via RBAC.

This issue affects all versions of cert-manager to have been released since at least v0.1.0 (since pem.Decode is core functionality for cert-manager). All supported releases are patched.

Patches

The fixed versions are v1.16.2, v1.15.4 and v1.12.14.

• master branch: https://github.com/cert-manager/cert-manager/pull/7400
• release-1.16 branch: https://github.com/cert-manager/cert-manager/pull/7401
• release-1.15 branch: https://github.com/cert-manager/cert-manager/pull/7402
• release-1.12 branch: https://github.com/cert-manager/cert-manager/pull/7403

Workarounds

Ensure that RBAC is scoped correctly in your cluster. If a user is able to modify resources containing PEM data to be able to exploit this, it's like that those permissions are a bigger security threat than this issue - especially for Secret resources.

References

• Upstream issue: https://github.com/golang/go/issues/50116
• Similar issue: https://github.com/sigstore/sigstore/issues/198
• Google OSSFuzz: https://issues.oss-fuzz.com/issues/376728466

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4
• https://github.com/golang/go/issues/50116
• https://github.com/cert-manager/cert-manager/pull/7400
• https://github.com/cert-manager/cert-manager/pull/7401
• https://github.com/cert-manager/cert-manager/pull/7402
• https://github.com/cert-manager/cert-manager/pull/7403
• https://go.dev/issue/50116
• https://pkg.go.dev/vuln/GO-2024-3282
• https://github.com/cert-manager/cert-manager/commit/3a4c9eb55e2e43570679840bbe3217869fbc8efc
• https://github.com/cert-manager/cert-manager/commit/f22f78c8c0a64d718e203b326bc844c488ad7850
• https://github.com/advisories/GHSA-r4pg-vg54-wxx4

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.15.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression

• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.22.9 (#​7424, @​SgtCoDFish)
• Upgrade Go to 1.22.8, the latest available patch release (#​7406, @​SgtCoDFish)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.