← Back
GHSA-fcmh-qfxc-w685
Vulnerability in github.com/cloudnativelabs/kube-router (GHSA-fcmh-qfxc-w685)
Summary
vulnerability in github.com/cloudnativelabs/kube-router (GHSA-fcmh-qfxc-w685). Confidential information can be exposed externally. Exploitable via ``node.Annotations``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-fcmh-qfxc-w685** has been found in github.com/cloudnativelabs/kube-router.
Attackers can target a specific entry point like ``node.Annotations`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/cloudnativelabs/kube-router GHSA-fcmh-qfxc-w685" on the vendor's site.
GHSA-fcmh-qfxc-w685 (github.com/cloudnativelabs/kube-router) — CWE-532 /
Attack vector: local / no user interaction
Attack surface: `node.Annotations` / `fmt.Stringer` / `PeerConfig` / `PeerConfigs`
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-532) exists in github.com/cloudnativelabs/kube-router. Attackers reach the vulnerable code path via ``node.Annotations`` without authentication.
📍 Affected scope
github.com/cloudnativelabs/kube-router — . Attack surface: `node.Annotations` / `fmt.Stringer` / `PeerConfig` / `PeerConfigs`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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/cloudnativelabs/kube-router' .` 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
-
1Identify exposure identify
grep -r 'github.com/cloudnativelabs/kube-router' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/cloudnativelabs/kube-router` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/cloudnativelabs/kube-router
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/cloudnativelabs/kube-router/v2
[{"type":"SEMVER","events":[{"introduced":"2.7.0"},{"last_affected":"2.8.0"}]}]