Fixing issue #35530: Password Leak in Log Messages (#35584) #35609
+7
−5
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.
Backport #35584 by @shashank-netapp
Summary
The Gitea codebase was logging
Elasticsearch
andMeilisearch
connection strings directly to log files without sanitizing them. Since connection strings often contain credentials in the formatprotocol://username:password@host:port
, this resulted in passwords being exposed in plain text in log output.Fix:
util.SanitizeCredentialURLs()
function before logging them.Fixes: #35530