Categories
CVE-2023-32077 high CVSS 7.5

Vulnerability in github.com/gravitl/netmaker (CVE-2023-32077)

Summary

Vulnerability in github.com/gravitl/netmaker (CVE-2023-32077). Confidential information can be exposed externally. Mitigation: upgrade to 0.17.1 or later.

Original description

The description as published by the source.

Netmaker makes networks with WireGuard. Prior to versions 0.17.1 and 0.18.6, hardcoded DNS key usage has been found in Netmaker allowing unauth users to interact with DNS API endpoints. The issue is patched in 0.17.1 and fixed in 0.18.6. If users are using 0.17.1, they should run docker pull gravitl/netmaker:v0.17.1 and docker-compose up -d. This will switch them to the patched users. If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later. As a workaround, someone who is using version 0.17.1 can pull the latest docker image of the backend and restart the server.

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-32077 has been found in github.com/gravitl/netmaker.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/gravitl/netmaker to 0.17.1 or later.
If unsure, ask your IT team or search "github.com/gravitl/netmaker CVE-2023-32077" on the vendor's site.

CVE-2023-32077 (github.com/gravitl/netmaker) — CWE-321 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.17.1 — apply immediately
Workaround: If using 0.17.1, can just pull the latest docker image of backend and restart server.
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-321) exists in github.com/gravitl/netmaker.

📍 Affected scope

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

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.17.1.

🛡️ Workaround

Workaround: If using 0.17.1, can just pull the latest docker image of backend and restart server.

🔍 Detection

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

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

  2. 2
    Apply temporary workaround mitigate
    If using 0.17.1, can just pull the latest docker image of backend and restart server.

    パッチが適用されるまでの応急処置として、If using 0.17.1, can just pull the latest docker image of backend and restart server. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade github.com/gravitl/netmaker to 0.17.1

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

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

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

Affected packages

go github.com/gravitl/netmaker
[{"type":"SEMVER","events":[{"introduced":"0.18.0"},{"fixed":"0.18.6"}]}]

References

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