fix(api): secure exception handling and prevent information disclosure#1106
Open
RinZ27 wants to merge 1 commit intolangflow-ai:mainfrom
Open
fix(api): secure exception handling and prevent information disclosure#1106RinZ27 wants to merge 1 commit intolangflow-ai:mainfrom
RinZ27 wants to merge 1 commit intolangflow-ai:mainfrom
Conversation
github-actions
bot
added
backend
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
1 participant
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.
Error handling in OAuth and chat endpoints was returning raw exception messages to clients, which could lead to sensitive information disclosure about the system's internal structure or environment.
Replacing these raw responses with generic, user-friendly error messages ensures the API remains robust and secure. Full tracebacks are now correctly routed to the server logs via the existing logger for debugging purposes, while the client only sees a high-level error state.
All security-sensitive paths in
src/api/auth.py,src/api/chat.py,src/api/connectors.py, andsrc/api/documents.pyhave been updated to follow this pattern. This approach prevents potential attackers from gaining insights into the application's underlying logic or configuration through error strings.Verified the changes locally. All API endpoints now return sanitized JSON responses on failure.