Potential fix for code scanning alert no. 6: Information exposure through an exception #123
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.
Potential fix for https://github.com/TilmanGriesel/chipper/security/code-scanning/6
To fix the problem, we need to modify the code to ensure that detailed exception information is not exposed to the user. Instead, we should log the detailed error message on the server and return a generic error message to the user. This can be achieved by updating the
except
block to remove the detailed exception message from theerror_response
.handle_standard_response
function, update theexcept
block to remove the detailed exception message from theerror_response
.logger.error
call.Suggested fixes powered by Copilot Autofix. Review carefully before merging.