← Back
GHSA-52cq-7v8r-62c6
Vulnerability in gmaps-mcp (GHSA-52cq-7v8r-62c6)
Summary
vulnerability in gmaps-mcp (GHSA-52cq-7v8r-62c6). Risk of unauthorized operations or information disclosure. Exploitable via `X-API-Key header`. Mitigation: upgrade to `0.1.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-52cq-7v8r-62c6** has been found in gmaps-mcp.
Attackers can target a specific entry point like `X-API-Key header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade gmaps-mcp to **0.1.3** or later.
If unsure, ask your IT team or search "gmaps-mcp GHSA-52cq-7v8r-62c6" on the vendor's site.
GHSA-52cq-7v8r-62c6 (gmaps-mcp) — CWE-20 /
Attack surface: X-API-Key header / `e671db68c804c9e67d51582d3280839ffa65f127` / `server.py` / `MCP_API_KEY`
Patched: `0.1.3` — 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-20) exists in gmaps-mcp. Attackers reach the vulnerable code path via `X-API-Key header` without authentication.
📍 Affected scope
gmaps-mcp — . Attack surface: X-API-Key header / `e671db68c804c9e67d51582d3280839ffa65f127` / `server.py` / `MCP_API_KEY`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.1.3**.
🛡️ 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 'gmaps-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 'gmaps-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `gmaps-mcp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade gmaps-mcp to 0.1.3ステージング環境で 0.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
gmaps-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.3"}]}]
References
- web https://github.com/arthurkatcher/google-maps-mcp/security/advisories/GHSA-52cq-7v8r-62c6
- web https://github.com/arthurkatcher/google-maps-mcp/commit/00d872507c78e8116bbf9de7be7cd112945c0fd8
- web https://github.com/arthurkatcher/google-maps-mcp/commit/3ae32643da469f962e67e8ef9726cd4d9bf4587d
- web https://github.com/advisories/GHSA-52cq-7v8r-62c6