Thousands of images on Docker Hub leak auth secrets, private keys
bleepingcomputer.com
The result of the study can be found at https://arxiv.org/pdf/2307.03958.pdf.
You are viewing a single comment
The result of the study can be found at https://arxiv.org/pdf/2307.03958.pdf.
Isn't it about people pushing their keys to public? I feel like this doesn't affect the pulling side
Itβs actually how people build their images, in which some include sensitive data (when they should definitely not). Itβs the same problem as exposed S3 buckets actually, nothing wrong with docker in itself.
aws s3 sync s3://barrys-nudes/ .
Have you seen the instructions on how to build the Lemmy images? That's some crazy shit ...
Actually yes, I had a look at them since i wanted to write HelmCharts for the community. Thatβs also where the community can step up, it can only be better π
I actually started looking into creating own Docker images because of how bad Lemmy's Docker instructions are. I'm not even close to anything usable, though ...
I understand! If you need help to do that (or someone to contribute), hit me up ! π
I guess it depends, if it's a secret in use for the image, an attacker might use it to attack a pulled instance if the user deploying it didn't change the secret. Kind of like an unchanged initial password.