Vulnerability in github.com/cert-manager/cert-manager (CVE-2024-12401)
Summary
Vulnerability in github.com/cert-manager/cert-manager (CVE-2024-12401). Risk of unauthorized operations or information disclosure. Exploitable via pem.Decode. Mitigation: upgrade to 1.16.2 or later.
Original description
The description as published by the source.
A flaw was found in the cert-manager package. This flaw allows an attacker who can modify PEM data that the cert-manager reads, for example, in a Secret resource, to use large amounts of CPU in the cert-manager controller pod to effectively create a denial-of-service (DoS) vector for the cert-manager in the cluster.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-12401 has been found in github.com/cert-manager/cert-manager.
Attackers can target a specific entry point like pem.Decode over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade github.com/cert-manager/cert-manager to 1.16.2 or later.
If unsure, ask your IT team or search "github.com/cert-manager/cert-manager CVE-2024-12401" on the vendor's site.
CVE-2024-12401 (github.com/cert-manager/cert-manager) — CWE-20 / CVSS v3 4.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: pem.Decode
Patched: 1.16.2 — apply immediately
Workaround: Ensure that RBAC is scoped correctly in your cluster.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in github.com/cert-manager/cert-manager. Attackers reach the vulnerable code path via pem.Decode.
Check the vendor advisory for the affected versions of github.com/cert-manager/cert-manager. Attack surface: pem.Decode.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.16.2.
Workaround: Ensure that RBAC is scoped correctly in your cluster.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cert-manager/cert-manager' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/cert-manager/cert-manager' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/cert-manager/cert-managerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure that RBAC is scoped correctly in your cluster.パッチが適用されるまでの応急処置として、Ensure that RBAC is scoped correctly in your cluster. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/cert-manager/cert-manager to 1.16.2ステージング環境で 1.16.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- report bugzilla.redhat.com
- web github.com
- web go.dev
- web pkg.go.dev
- web github.com
- web github.com
- web github.com
- web access.redhat.com
- web catalog.redhat.com