Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-54365 high CVSS 7.5

Vulnerability in github.com/traefik/traefik (CVE-2023-54365)

Summary

Vulnerability in github.com/traefik/traefik (CVE-2023-54365). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.0-beta4 or later.

Original description

The description as published by the source.

Traefik before 2.10.5 and 3.0.0 is affected by a denial-of-service vulnerability in HTTP/2 request handling inherited from the Go standard library's HTTP/2 implementation (CVE-2023-44487 / CVE-2023-39325, the 'Rapid Reset' technique). A remote attacker can rapidly create and cancel HTTP/2 streams to exhaust server resources and cause service unavailability.

Source: NIST National Vulnerability Database 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-2023-54365 has been found in github.com/traefik/traefik.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/traefik/traefik to 3.0.0-beta4 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik CVE-2023-54365" on the vendor's site.

CVE-2023-54365 (github.com/traefik/traefik) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.0-beta4 — apply immediately
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-400) exists in github.com/traefik/traefik.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.0-beta4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/traefik/traefik' . 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/traefik/traefik' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/traefik/traefik を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/traefik/traefik to 3.0.0-beta4

    ステージング環境で 3.0.0-beta4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go github.com/traefik/traefik
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-beta4"}]}]
Bitnami golang
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.20.10"},{"introduced":"1.21.0"},{"fixed":"1.21.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details