(CodeQL) Fixed finding: "Prevent information leak of stack trace details to HTTP responses" #6
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.
Remediation
This change fixes "Prevent information leak of stack trace details to HTTP responses" (id = stack-trace-exposure) identified by CodeQL.
Details
This change prevents stack trace information from reaching the HTTP response, which could leak code internals to an attacker and aid in further profiling and attacks.
Have you ever seen an error page and thought, "Wow, I certainly shouldn't be seeing all these code details?" That's this problem.
Switching to a safe signature that doesn't leak anything is easy and the changes look something like this:
More reading
🧚🤖 Powered by Pixeebot
Feedback | Community | Docs | Codemod ID: codeql:java/stack-trace-exposure