Draft
fix: replace raw exception strings in HTTP responses (CWE-209)#95
Conversation
Copilot
AI
changed the title
[WIP] Fix code scanning alert #57
fix: replace raw exception strings in HTTP responses (CWE-209)
Jul 21, 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.
Raw
str(exc)/str(e)values were being stored in state objects that get serialised and returned to HTTP clients, leaking internal implementation details (file paths, class names, internal logic) viaGET /api/user-scanner/full-scan/statusand the unauthenticatedGET /api/settingsendpoint.Changes
simple_org_chart/app_main.py— three call sites replaced with generic error strings:_background_full_scan: scan state dict error fieldtrigger_update:mark_data_update_finishederror argclear_cached_data:mark_data_update_finishederror argServer-side
logger.error(...)calls are preserved in all three locations, so full exception details remain available to operators in logs.