fix(security): add rate limiting to /api/extract to prevent API key exhaustion#968
Open
Vedhant26 wants to merge 1 commit into
Open
fix(security): add rate limiting to /api/extract to prevent API key exhaustion#968Vedhant26 wants to merge 1 commit into
Vedhant26 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔒 Fix: Add Rate Limiting to AI Extraction Endpoint
Closes #927
Security Issue
The
/api/extractendpoint (which connects to the Gemini AI API) was completely unauthenticated and had no rate limiting. This meant a malicious user could spam the endpoint, causing the server to exhaust theGEMINI_API_KEYquota or rack up billing charges, leading to a Denial of Service (DoS) for legitimate users.Solution
express-rate-limit.extractLimitermiddleware explicitly applied toapp.post('/api/extract', ...).