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