We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, I'm security researcher that recently works on your docker image d8sychain/mediawiki on DockerHub.
After I set up the image, it seems like /includes directories are open to public access.
However, it should not be expose. Since it contains .php files, the attacker may access them and analyze potential security holes in them, as mentioned in https://www.wordfence.com/learn/understanding-php-vulnerabilities/ and https://www.cvedetails.com/vulnerability-list/vendor_id-74/product_id-128/PHP-PHP.html.
Would it be better to block these access in your docker image? Thanks!
Best, -ct
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, I'm security researcher that recently works on your docker image d8sychain/mediawiki on DockerHub.
After I set up the image, it seems like /includes directories are open to public access.
However, it should not be expose. Since it contains .php files, the attacker may access them and analyze potential security holes in them, as mentioned in https://www.wordfence.com/learn/understanding-php-vulnerabilities/ and https://www.cvedetails.com/vulnerability-list/vendor_id-74/product_id-128/PHP-PHP.html.
Would it be better to block these access in your docker image? Thanks!
Best,
-ct
The text was updated successfully, but these errors were encountered: