Impact
Rosco currently does not property mask AWS hard coded secrets when doing packer builds. This can lead to exposure of sensitive AWS credentials in log files and bake job history in redis.
Patches
Fixed in Rosco and backported to prior releases of spinnaker for 1.29, 1.28 and 1.27
Workarounds
It's recommended to use short lived credentials via role assumption and IAM profiles. Additionally credentials can be set in /home/spinnaker/.aws/credentials and /home/spinnaker/.aws/config as a volume mount for Rosco pods vs. setting credentials in roscos bake config properties. Last even with those it's recommend to use IAM Roles vs. long lived credentials. This drastically mitigates the risk of credentials exposure.
If users have used static credentials, it's recommended to purge any bake logs for AWS, evaluate whether AWS_ACCESS_KEY, SECRET_KEY and/or other sensitive data has been introduced in log files and bake job logs. Then, rotate these credentials and evaluate potential improper use of those credentials.
References
Advisory on Rosco microservice
Impact
Rosco currently does not property mask AWS hard coded secrets when doing packer builds. This can lead to exposure of sensitive AWS credentials in log files and bake job history in redis.
Patches
Fixed in Rosco and backported to prior releases of spinnaker for 1.29, 1.28 and 1.27
Workarounds
It's recommended to use short lived credentials via role assumption and IAM profiles. Additionally credentials can be set in
/home/spinnaker/.aws/credentialsand/home/spinnaker/.aws/configas a volume mount for Rosco pods vs. setting credentials in roscos bake config properties. Last even with those it's recommend to use IAM Roles vs. long lived credentials. This drastically mitigates the risk of credentials exposure.If users have used static credentials, it's recommended to purge any bake logs for AWS, evaluate whether AWS_ACCESS_KEY, SECRET_KEY and/or other sensitive data has been introduced in log files and bake job logs. Then, rotate these credentials and evaluate potential improper use of those credentials.
References
Advisory on Rosco microservice