Server Status Page Exposed
A web server status page, such as Apache's /server-status, is publicly reachable and shows live details of the server and the requests it is handling.
| Severity | Low |
| CVSS 3.1 | 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1592.002 Software |
| Category | Information Disclosure |
Description
Web servers can publish a status page for administrators, and this page is reachable from untrusted networks without authentication. The most common is the Apache HTTP Server status page provided by mod_status, usually at /server-status; other servers offer simpler equivalents, such as the nginx stub_status page, which shows only connection counts and is of little value to an attacker. A frequent cause is an access rule such as Require local on a server that sits behind a reverse proxy on the same host: every request then arrives from the local address and passes the rule.
With extended status enabled, the Apache page lists every worker's current request, showing the client's IP address, the virtual host and the full request line, including any query string. An attacker can watch the requests other users are making: their IP addresses, which are personal data, and the addresses they request, which can include session identifiers, password reset tokens or other secrets passed in query strings. What is disclosed depends on the traffic at the moment the page is viewed, though repeated polling gathers more. The page also reveals hidden paths, virtual host names and software versions that help with targeting, along with the server's uptime, load and traffic figures, and the related /server-info page from mod_info shows the server's loaded configuration.
The page is found by requesting common paths such as /server-status, /server-status?auto, /server-info and /nginx_status, and most web scanners report it.
Remediation
Disable status pages where they are not needed, and restrict them where they are:
- On Apache, disable
mod_statusandmod_infoif they are not used, for example witha2dismod status infoon Debian and Ubuntu, or by commenting out theirLoadModulelines. - Where the status page is needed, restrict it to a management network or to authenticated administrators, and do not rely on
Require localwhen a proxy runs on the same host. - Set
ExtendedStatus Offunless the per-request detail is needed, so that client addresses and requested addresses are not shown. - Block the status paths at any reverse proxy or load balancer in front of the server.
- Avoid passing tokens or other secrets in query strings, so that they cannot appear in status pages or logs.
Confirm the fix by requesting the status paths from an untrusted network: each should return 403 or 404.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.