Outdated Apache HTTP Server
The web server runs an Apache HTTP Server release that is missing published security fixes.
| Severity | High |
| CVSS 3.1 | 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services |
| Category | Outdated Components |
Description
The web server runs a release of Apache HTTP Server (httpd) that predates fixes for one or more published vulnerabilities. The Apache project's security pages list each flaw, its severity and the release that fixes it, and an attacker can use public exploits for the unfixed vulnerabilities against the web server, which is usually internet-facing.
Past issues show what this can allow, depending on the flaws and the modules in use: path traversal that allowed files outside the document root to be read and, where CGI was enabled, code to be run on the server (CVE-2021-41773 and its incomplete fix); server-side request forgery and request smuggling through mod_proxy, which let internal systems be reached through the proxy and requests be smuggled past front-end controls; flaws in mod_rewrite, mod_lua and the HTTP/2 module; and denial of service that takes the service offline. Many apply only when a particular module or configuration is in use. Several httpd vulnerabilities, including CVE-2021-41773, have been widely exploited and are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue. Code execution runs with the privileges of the httpd worker account, so a hardened configuration and least privilege limit the impact but do not remove it.
The finding is usually raised from the version in the Server response header or on default error pages, and scanners report one result per advisory affecting that version. Linux distributions such as Red Hat Enterprise Linux and Debian backport security fixes into the httpd version they ship without changing its version number, so a server announcing an old version may be fully patched; results should be confirmed against the distribution's advisories or, better, by an authenticated check of the installed package. Apache httpd is also embedded in other products, such as management consoles and appliances, where it is updated by the product's vendor.
Remediation
Update httpd through the channel it was installed from:
- Where httpd comes from the operating system, install the distribution's latest httpd or apache2 package and restart the service. Do not replace it with a source build just to satisfy a version check.
- Where it was built from source or comes from a third-party package, upgrade to the current release of a supported branch from the Apache HTTP Server project, review the changes affecting the modules in use, and restart. Where httpd is embedded in another product, apply that vendor's update.
- Disable modules that are not needed, such as
mod_proxy,mod_cgiandmod_lua, and keepRequire all deniedon the filesystem root directory, which limited the impact of past path traversal flaws. - Set
ServerTokens ProdandServerSignature Offto stop the version being advertised; this hides the version but does not fix anything. - Subscribe to the Apache httpd announcements or the distribution's security notices so that future fixes are applied promptly.
Where an update must wait, a web application firewall rule can block known exploit patterns for a specific advisory as an interim measure. Confirm the fix by checking the installed package or the version reported by httpd -v or apache2ctl -v against the advisories.
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.