Potential fix for code scanning alert no. 2: Clear-text logging of sensitive information #124
Conversation
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
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
fhonza
approved these changes
Nov 20, 2025
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.
Potential fix for https://github.com/DCSO/fever/security/code-scanning/2
The best way to fix this problem is to avoid including sensitive credentials—in this case, the MongoDB password—in any log statements. Specifically, in
MakeMongoSlurper, the log line on 265 should not record the value ofurlas it contains sensitive information. Instead, you can log a sanitized version of the connection string, or omit theurlfield entirely and just report the host and database, which are not sensitive. This change should be made only to line 265, replacing the log call so that it does not expose the password. No changes to the overall logic are required, and no new dependencies are necessary. We can use Go's string manipulation to construct a sanitized string if useful, or simply log the properties individually.Suggested fixes powered by Copilot Autofix. Review carefully before merging.