[Bug]: GraphQL has no complexity or alias limit

未關閉
#125 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
graphql, rust
領域
backend, security

研究方向

Start at src/api/schema.rs around line 112, where limit_depth(16) is set on the schema builder, and read the surrounding schema construction plus the expensive root fields (library listings, probes) mentioned in the issue. Read the async-graphql docs for limit_complexity and the complexity field attribute, then decide a cost budget and whether alias/root-field caps are needed. Done means a schema test showing an over-cost query (e.g. one field aliased hundreds of times) is rejected while normal queries still pass; no such test file exists yet, so one will have to be added.

由索引模型根據 Issue 內容生成。

描述

bug

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a code review session with @PhrolovaMoe. It was found by reading the code and hasn't been reproduced on a running server.

Version

0.40.0 (feat/desktop, 017a837b)

Area

Other

What happened?

The schema only sets limit_depth(16) (src/api/schema.rs:112). One request can alias an expensive field (like library listings or probes) hundreds of times, and any signed-in user can make the server do a lot of work with it.

Expected behavior

Requests over a reasonable cost are rejected.

Suggested fix

Add .limit_complexity(…) (with complexity on expensive fields) and cap aliases or the number of root fields per request.

主要語言
TypeScript
星號
4
分支
1
平均合併
4 小時 49 分鐘
30 天內合併 PR
5

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

tinystream-dev/tinystream 的其他 Issue

查看 tinystream-dev/tinystream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。