Outdated nginx

The web server or reverse proxy runs an nginx release that is missing published security fixes.

SeverityMedium
CVSS 3.16.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H Open in the calculator
CVSS 4.08.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1499.004 Application or System Exploitation, T1190 Exploit Public-Facing Application
CategoryOutdated Components

Description

The web server or reverse proxy runs a release of nginx that predates fixes for one or more published vulnerabilities. The nginx project lists each advisory with the vulnerable and fixed versions and its own severity rating. Most nginx advisories affect particular modules or features rather than the core server, for example the HTTP/2 and HTTP/3 implementations, the mp4 module, the DNS resolver, the mail proxy and SSL session handling, so whether an advisory applies depends on the modules built in and the configuration, and the risk is low where the affected modules are not enabled.

An attacker who can send requests to the server can exploit unfixed flaws in the modules in use. The usual result is denial of service, as crafted requests repeatedly crash worker processes, or the disclosure of fragments of worker memory that may contain other users' data or headers. Less often, memory is corrupted, and a small number of flaws, such as memory corruption in the resolver, could in principle allow code execution with the worker's privileges, although this has rarely been demonstrated. Where nginx fronts many applications, an outage affects all of them.

The finding is usually raised from the version in the Server header or on default error pages, and scanners report one result per advisory affecting that version, without checking whether the affected module is enabled. Linux distributions backport fixes into the nginx version they ship without changing the version number, so results should be confirmed against the distribution's advisories or an authenticated check of the installed package. nginx is also embedded in many products, such as Kubernetes ingress controllers, load balancers and appliances, which are updated by their vendors.

Remediation

Update nginx through the channel it was installed from:

  • Where nginx comes from the operating system, install the distribution's latest nginx package and reload or restart the service.
  • Where it comes from the nginx project's own packages or a source build, upgrade to the current stable or mainline release, rebuilding any third-party modules against it.
  • Where nginx is part of another product, such as an ingress controller or appliance, apply that product's update.
  • Disable modules and features that are not needed, such as HTTP/3, the mail proxy or mp4, and set server_tokens off; to stop the version being advertised; hiding the version does not fix anything.
  • Where an advisory gives a configuration workaround, such as disabling an affected feature, apply it until the update can be installed.

Confirm the fix with nginx -v or the installed package version, checked against the advisory for each reported CVE.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding