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.
Description
This PR addresses a security issue where S3 credentials used for Secondary Storage were being logged in plain text in CloudStack logs (
access.log
andmanagement-server.log
). Even when debug logging is enabled, secret credentials such asaccessKey
andsecretKey
should never appear in logs.Fix details:
accessKey
andsecretKey
from theS3TO
object before loggingDownloadCommand
inNfsSecondaryStorageResource.java
.NfsSecondaryStorageResourceTest.java
to verify that credentials are redacted.Steps to reproduce the issue:
/var/log/cloudstack/management/access.log
ormanagement-server.log
— credentials will be printed.Fixes: #10339
Types of changes
Bug Severity
How Has This Been Tested?
S3TO
and verifies thatsetAccessKey("***REDACTED***")
andsetSecretKey("***REDACTED***")
are called duringexecuteRequest
.