← Back
GHSA-g39v-cvjh-8fpf
Vulnerability in ha-mcp (GHSA-g39v-cvjh-8fpf)
Summary
vulnerability in ha-mcp (GHSA-g39v-cvjh-8fpf). Confidential information can be exposed externally. Exploitable via `GET /api/config`. Mitigation: upgrade to `7.4.1.dev456` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-g39v-cvjh-8fpf** has been found in ha-mcp.
Attackers can target a specific entry point like `GET /api/config` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade ha-mcp to **7.4.1.dev456** or later.
If unsure, ask your IT team or search "ha-mcp GHSA-g39v-cvjh-8fpf" on the vendor's site.
GHSA-g39v-cvjh-8fpf (ha-mcp) — CWE-552 /
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: GET /api/config / Authorization header / `ha_config_set_yaml` / `configuration.yaml`
Patched: `7.4.1.dev456` — 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-552) exists in ha-mcp. Attackers reach the vulnerable code path via `GET /api/config` without authentication.
📍 Affected scope
ha-mcp — . Attack surface: GET /api/config / Authorization header / `ha_config_set_yaml` / `configuration.yaml`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **7.4.1.dev456**.
🛡️ 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 `GET /api/config` requests with malformed payloads or SQL meta-characters. Run `grep -r 'ha-mcp' .` 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 'ha-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ha-mcp` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /api/config' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /api/config` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade ha-mcp to 7.4.1.dev456ステージング環境で 7.4.1.dev456 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /api/config on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
ha-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.5.0"}]}]
PyPI
ha-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.5.0"}]}]
References
- package https://github.com/homeassistant-ai/ha-mcp
- web https://github.com/homeassistant-ai/ha-mcp/security/advisories/GHSA-g39v-cvjh-8fpf
- web https://github.com/homeassistant-ai/ha-mcp/pull/1180
- web https://github.com/homeassistant-ai/ha-mcp/commit/09c524526b5f945638aa97de6218fadcd233023c
- web https://github.com/homeassistant-ai/ha-mcp/releases/tag/v7.4.1.dev456
- web https://github.com/homeassistant-ai/ha-mcp/releases/tag/v7.5.0
- web https://github.com/advisories/GHSA-g39v-cvjh-8fpf