Advisory

GHSA-r4pg-vg54-wxx4

Also known as: CVE-2024-12401, GO-2024-3282

Summary

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

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

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-11-20 20:48 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/cert-manager/cert-manager

Go · All systems

Affected

  • introduced 0, fixed 1.12.14 (semver)

Fixed versions

1.12.14

Fix

github.com/cert-manager/cert-manager

Go · All systems

Affected

  • introduced 1.13.0-alpha.0, fixed 1.15.4 (semver)

Fixed versions

1.15.4

Fix

github.com/cert-manager/cert-manager

Go · All systems

Affected

  • introduced 1.16.0-alpha.0, fixed 1.16.2 (semver)

Fixed versions

1.16.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences