fix(network): cap rooms, joiners and connections on the signaling server and the p2p host
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 38/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
- 領域
- networking, security
研究方向
Start with the cited room creation and joiner handling in modules/network/src/server/signaling.server.network.ts, then inspect joiner allocation in modules/network/src/server/peer-host.ts. Map the existing room and connection lifecycle before choosing limits and rate-limit behavior; the issue lists these goals but does not specify threshold values or validation rules. Done means enforcing agreed limits and validating bounded offers, with tests covering the listed abuse cases.
由索引模型根據 Issue 內容生成。
描述
Which package is this bug report for?
network
Issue description
Every host connection creates a room and every joiner is added, with no cap on rooms, joiners per room, connections per IP or frame rate. The 404-versus-upgrade answer tells whether a room exists and nothing throttles it (code space 32^6). On the p2p host, each new signal id that sends an offer allocates an RTCPeerConnection, with no limit on _joiners and no validation of offer / candidate.
Where:
modules/network/src/server/signaling.server.network.ts:66-69modules/network/src/server/signaling.server.network.ts:104-107modules/network/src/server/peer-host.ts:228-232
Evidence:
if (room !== null && !this._rooms.has(room)) { return new Response("Unknown room", { status: 404 }); }
this._rooms.set(room, { host: webSocket, joiners: new Map() });
...
if (!joiner) { if (message.type !== "offer") return; joiner = this.addJoiner(signalId); }
Suggested fix: Cap rooms, joiners per room, connections per IP and joiners not yet welcomed. Rate-limit failed room lookups and joiner frames. Check the offer shape and bound the sdp length.
Found during a code audit of main at be72076.
Code sample
No response
Versions
- Engine
mainat be72076 - pnpm 12.0.0, Node.js 26, Bun 1.3.14
Issue priority
High (immediate attention needed)
I have tested this issue on a development release
be72076
- 主要語言
- TypeScript
- 星號
- 7
- 分支
- 2
- 平均合併
- 1 天 17 小時
- 30 天內合併 PR
- 17
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NanoForge-dev/Engine 的其他 Issue
-
dependencies enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
NanoForge-dev/Engine#513 ·
維護者通常 1 天內回覆
-
bug chore tests
難度 2/5 1-3 小時 新手友好度 77/100
NanoForge-dev/Engine#511 ·
維護者通常 1 天內回覆
-
docs(network): TSDoc says ICE_SERVERS defaults to an empty list, the code uses public STUN servers未關閉documentation good first issue modules:network
難度 1/5 1 小時以內 新手友好度 88/100
NanoForge-dev/Engine#509 ·
維護者通常 1 天內回覆
-
documentation modules:ecs packages:asset packages:core
難度 2/5 1-3 小時 新手友好度 82/100
NanoForge-dev/Engine#508 ·
維護者通常 1 天內回覆
-
bug good first issue modules:music modules:sound
難度 2/5 1-3 小時 新手友好度 78/100
NanoForge-dev/Engine#505 ·
維護者通常 1 天內回覆
查看 NanoForge-dev/Engine 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
難度 1/5 1-3 小時 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
難度 2/5 1-3 小時 新手友好度 79/100
維護者通常 1 天內回覆
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
難度 2/5 1-3 小時 新手友好度 65/100
growilabs/growi#12246 · 3 則留言 ·
維護者通常 1 天內回覆
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 則留言 ·
維護者通常 1 天內回覆