Potential fix for code scanning alert no. 4: Information exposure through an exception #28
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/GitTimeraider/Directadmin-Emailforwarder/security/code-scanning/4
To fix the problem, we should ensure that exception details are not sent to the user in API responses. Instead, return a generic error message and log the actual exception details on the server for debugging. Specifically, in
DirectAdminAPI.create_forwarder, change the return value in the exception handler fromFalse, str(e)toFalse, "An error occurred while creating the forwarder". The detailed exception should still be logged server-side. No changes are needed inapp/main.pysince it already returns a generic error message in the outer exception handler, but the error returned fromcreate_forwardershould also be generic.Suggested fixes powered by Copilot Autofix. Review carefully before merging.