Skip to content
This repository has been archived by the owner on Nov 19, 2021. It is now read-only.

Risky data exposed to public access #32

Open
conf-test opened this issue May 3, 2021 · 0 comments
Open

Risky data exposed to public access #32

conf-test opened this issue May 3, 2021 · 0 comments

Comments

@conf-test
Copy link

Hi,

I'm a security researcher and am doing some study of public docker images. I found some misconfigurations in your docker image smmccabe/docker may expose some sensitive data. I want to report these potential issues to you so you can fix them if necessary.

The data exposure I found includes:

  1. git files: like /imagick/.gitignore, /imagick/.git/*,
  2. docker files: like /imagick/docker-compose.yml , /imagick/docker/fedora/Dockerfile, /imagick/docker/developing/Dockerfile, /imagick/docker/installImageMagick.sh

Would it be better to block these accesses in your docker image? If you want, I can also help fix them by creating pull requests on your git repo. Please let me know what you think. Thanks!

Best Regards,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant