Skip to content

fix(security): resolve persistent Missing rate limiting #13#113

Merged
NeuroKoder3 merged 2 commits into
mainfrom
fix/codeql-missing-rate-limiting-13-followup
May 12, 2026
Merged

fix(security): resolve persistent Missing rate limiting #13#113
NeuroKoder3 merged 2 commits into
mainfrom
fix/codeql-missing-rate-limiting-13-followup

Conversation

@NeuroKoder3
Copy link
Copy Markdown
Owner

Summary

  • replace separate authRateLimitHook + authHook registrations with one authWithRateLimit preHandler
  • explicitly call req.rateLimit() in the same preHandler that invokes authorization
  • target persistent CodeQL alert js/missing-rate-limiting reported at server/src/index.js

Test plan

  • npm --prefix server run lint
  • npm --prefix server run test

Replace separate auth hook registration with a single preHandler wrapper that calls req.rateLimit() before authorization so CodeQL can directly verify throttling at the flagged handler location.

Co-authored-by: Cursor <cursoragent@cursor.com>
Comment thread server/src/index.js Fixed
…hook

Attach rate limiting and authorization as route preHandlers for non-public routes to make throttling explicit at route registration time and address persistent CodeQL missing-rate-limiting findings.

Co-authored-by: Cursor <cursoragent@cursor.com>
@NeuroKoder3 NeuroKoder3 merged commit f27d46b into main May 12, 2026
15 checks passed
@NeuroKoder3 NeuroKoder3 deleted the fix/codeql-missing-rate-limiting-13-followup branch May 12, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants