fix(chat): add input length validation to prevent payload abuse#246
Merged
Userunknown84 merged 1 commit intoJun 24, 2026
Merged
Conversation
|
@devprashant19 is attempting to deploy a commit to the Aditya Sharma's projects Team on Vercel. A member of the Team first needs to authorize it. |
Userunknown84
approved these changes
Jun 24, 2026
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.
Description
This PR resolves the missing input validation vulnerability on the LLM
/chatendpoint. Previously, user input was passed directly to the Groq API without size restrictions, opening the application up to potential token exhaustion or billing spike attacks through excessively large payloads.Changes
messageinput inbackend/routes/chatRoutes.js.400 Bad Requestbefore sending anything to Groq.Related Issues
Type of Change
Pre-submission Checklist