Fix code scanning alert no. 1: Information exposure through an exception #4619
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.
Fixes https://github.com/telefonicaid/fiware-orion/security/code-scanning/1
To fix the problem, we need to ensure that detailed error messages, including stack traces, are not exposed to the end users. Instead, we should log the detailed error information on the server and return a generic error message to the user. This can be achieved by modifying the
record_request
function to log the exception details and append a generic error message to the response string.record_request
function to log the exception details instead of appending them to the response string./dump
endpoint returns the accumulated data without exposing sensitive error information.Suggested fixes powered by Copilot Autofix. Review carefully before merging.