1. Proposed title of this feature request
Disable directory listing for /pub directory on satellite Capsule 6 using custom-hiera.
The same for the Satellite Server was addressed in the following RFE:
This time would be necessary to do the same for the Capsule server.
3. What is the nature and description of the request?
Our internal vulnerability compliance program is detecting that the /pub directory has Indexes enabled, which can lead to other security issues. We are required to remediate this issue (on port 80 and 443) in order to be complaint with our Information Security policies.
4. Why does the customer need this? (List the business requirements here)
Web Directories Listable -- The Web server has some listable directories. Very sensitive information can be obtained from directory listings. A remote user may exploit this vulnerability to obtain very sensitive information on the host. The information obtained may assist in further attacks against the host. Disable directory browsing or listing for all directories.
5. How would the customer like to achieve this? (List the functional requirements here)
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 6.3, 6.4 & 6.5
9. Is the sales team involved in this request and do they have any additional input?
10. List any affected packages or components.
11. Would the customer be able to assist in testing this functionality if implemented?
Created redmine issue https://projects.theforeman.org/issues/27689 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27689 has been resolved.
Build Version: 6.7 Snap10
Verified successfully on the capsule server, Accessing the https://<capserver>/pub & http://<capserver>/pub using a web browser and it returns forbidden.
Files of the pub directory are still downloadable if the user knows their path and name.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.