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