Internal IP Address Disclosure

Responses reveal private IP addresses or internal host names of the servers behind the application, giving an attacker details of the internal network.

SeverityLow
CVSS 3.13.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.06.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
CWECWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1590.005 IP Addresses
CategoryInformation Disclosure

Description

The application or its supporting infrastructure discloses private (RFC 1918) IP addresses, or internal host names, of the servers behind it. Common sources are the Location and Content-Location headers in responses to requests sent without a Host header or as HTTP/1.0; headers added by load balancers and proxies, such as Via or custom headers naming the back-end server, and persistence cookies set by load balancers that encode the back-end address, which can also show how many back-end servers there are and how they are named; error messages, page content and comments; and the challenge in NTLM authentication, which reveals internal domain and host names.

Such a disclosure gives an attacker no access by itself, but it helps them map the internal network and its addressing, aim server-side request forgery or other flaws that reach internal systems, and recognise which systems they have reached if they later gain a foothold.

The issue is identified by inspecting responses for private address ranges and internal names, including responses to deliberately unusual requests. Scanners commonly report it from the Location header of a redirect.

Remediation

Stop the application and its infrastructure from including internal addresses and names in responses:

  • Configure web servers to build redirects and other self-referencing headers from the public host name rather than the server's own address: on IIS, set the alternateHostName attribute of the serverRuntime section to the public host name; on Apache, set ServerName and, where appropriate, UseCanonicalName On; on nginx, review server_name_in_redirect and absolute_redirect.
  • Remove or rewrite headers added by load balancers and reverse proxies that name back-end servers, and configure load balancer persistence cookies to be encrypted or to carry an opaque value.
  • Replace detailed error messages with generic ones, and remove internal addresses from comments and page content.
  • Where NTLM authentication is offered to the internet, consider whether it is needed there.

Confirm the fix by repeating the requests that produced the disclosure, including HTTP/1.0 requests without a Host header, and checking that no private address or internal name is returned.

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 Web Applications Findings

Every Web Applications finding