Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2024-12401 medium CVSS 4.4

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.

AI summary snake-internal / snake-material-v2

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.
❓ What is the problem
**A vulnerability** (CWE-20) exists in github.com/cert-manager/cert-manager. Attackers reach the vulnerable code path via ``pem.Decode`` without authentication.
📍 Affected scope
github.com/cert-manager/cert-manager — . Attack surface: `pem.Decode`.
🔥 Severity
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.16.2**.
🛡️ Workaround
Workaround: Ensure that RBAC is scoped correctly in your cluster.
🔍 Detection
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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    Ensure that RBAC is scoped correctly in your cluster.

    パッチが適用されるまでの応急処置として、Ensure that RBAC is scoped correctly in your cluster. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade github.com/cert-manager/cert-manager to 1.16.2

    ステージング環境で 1.16.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/cert-manager/cert-manager
[{"type":"SEMVER","events":[{"introduced":"1.16.0-alpha.0"},{"fixed":"1.16.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →