CVE-2021-47718
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openbmcs | openbmcs | 2.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-548 | The product inappropriately exposes a directory listing with an index of all the resources located inside of the directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in OpenBMCS 2.4 allows unauthenticated attackers to access sensitive files by exploiting directory listing functionality. Attackers can browse directories such as /debug/ and /php/ to find configuration files, database credentials, and system information.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of sensitive information, including configuration files and database credentials, which could be used to further compromise the system or gain unauthorized access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to access directory listings on the OpenBMCS web interface, specifically targeting directories such as /debug/ and /php/. For example, using curl or wget commands to request these directories can reveal if directory listing is enabled and sensitive files are exposed. Example commands include: curl -v http://<target-ip>/debug/ or wget --spider http://<target-ip>/php/. If directory contents are listed instead of a 403 Forbidden or 404 Not Found error, the system is vulnerable. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling directory listing on the web server hosting OpenBMCS, particularly for sensitive directories like /debug/ and /php/. This can be done by configuring the web server (Apache or nginx) to turn off directory indexing (e.g., using 'Options -Indexes' in Apache or 'autoindex off;' in nginx). Additionally, restrict access to sensitive directories via proper access controls or authentication mechanisms to prevent unauthenticated access. [1, 2, 3]