Potential fix for code scanning alert no. 1: Clear-text logging of sensitive information #255
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/unitaryfoundation/metriq-api/security/code-scanning/1
To fix the issue, we need to ensure that sensitive information, such as the database password, is not logged. Instead of logging the full connection string, we can log a sanitized version that excludes sensitive details. This can be achieved by constructing a version of the connection string that omits the password before logging it.
The fix involves:
metriq-api/index.js
to log a sanitized version ofconfig.pgConnectionString
.Suggested fixes powered by Copilot Autofix. Review carefully before merging.