| Audience: DocuShare administrators and security teams |
Resolve Scanner Findings for Missing HTTP Security Headers on DocuShare Ports 8080 and 9001
Overview
A vulnerability scanner may report that responses from a DocuShare server on port 8080 or port 9001 do not include the X-Content-Type-Options HTTP security header. These findings report a missing response header rather than a specific software flaw. The two ports belong to different components, so each has its own explanation and action.
| Summary: Port 8080 is the DocuShare web server. Install the latest DocuShare 7.7 patch, and restrict which computers can reach the port. Port 9001 is the IDOL search engine. The finding is not exploitable, and blocking ports 9000, 9001, and 9002 at the Windows firewall clears it. |
Findings Covered
| Scanner finding | Port | Component | Observation | Resolution |
| HTTP Security Header Not Detected (Qualys QID 11827) | 8080 | DocuShare web server (Tomcat) | X-Content-Type-Options header missing | Install DocuShare 7.7 Patch 5 or later. Restrict which computers can reach port 8080. |
| Missing HTTP Security Headers in 403 Responses (Qualys QID 735183) | 9001 | IDOL search engine index port | X-Content-Type-Options header missing on the 403 response | Not exploitable. Block inbound ports 9000, 9001, and 9002 at the Windows firewall. |
Port 8080: DocuShare Web Server
Port 8080 is the connector on which the DocuShare web server (Apache Tomcat) listens. The page the scanner receives is the DocuShare start page. The X-Content-Type-Options: nosniff header tells browsers not to guess a file's content type, which reduces content-type confusion attacks.
DocuShare 7.7 Patch 5 and later add a security-header filter to the DocuShare and ConnectKey web applications, which sends X-Content-Type-Options: nosniff. Installing the latest 7.7 patch resolves the finding.
1. Check your DocuShare release and patch level. If you run DocuShare 7.7 earlier than Patch 5, install the latest DocuShare 7.7 patch. Follow the instructions supplied with the patch.
2. After the patch is installed and DocuShare is running, verify the header. From a computer that can reach the server, run: curl.exe -I http://<DocuShare server name>:8080/
3. Confirm that the response includes X-Content-Type-Options: nosniff.
4. Restrict which computers can reach port 8080. IIS does not use this port: the IIS web server bridge connects to DocuShare through port 8009. Before you block port 8080, check whether any computer or device connects to DocuShare with an address that includes :8080 and allow only those.
5. Confirm that users can still sign in through your normal web address, then run the scan again.
| Note: HTTP Strict Transport Security (HSTS) is sent only over HTTPS, so it does not appear on port 8080, which uses HTTP. Configure HSTS on the IIS HTTPS site. See the article "Configure HTTP Strict Transport Security (HSTS) for Xerox DocuShare". |
DocuShare 8.1 sends the X-Content-Type-Options: nosniff header without an additional patch. DocuShare 8.0 does not. On DocuShare 8.0, or if you cannot install the 7.7 patch immediately, restrict port 8080 as described in step 4. For other DocuShare releases, contact Xerox DocuShare Support.
Port 9001: IDOL Search Engine
Port 9001 is the index port of the IDOL search engine, which DocuShare uses only from the same server. The shipped IDOL configuration accepts connections only from 127.0.0.1, the server itself. IDOL is a third-party search engine and has no DocuShare setting for response headers.
The missing X-Content-Type-Options header on port 9001 is not exploitable. IDOL returns a fixed "403 Forbidden" page to any client other than the DocuShare server, and that page contains no DocuShare content. Blocking the IDOL ports at the Windows firewall is recommended to clear the scan finding and reduce exposure, not to correct an exploitable flaw.
This section applies to sites that use the IDOL search engine. It does not apply to sites that use Solr.
1. On the DocuShare server, open <DSHome>\IDOLServer\IDOL\AutonomyIDOLServer.cfg in a text editor.
2. Confirm that the QueryClients, AdminClients, and IndexClients settings are still 127.0.0.1. If they have been changed, contact Xerox DocuShare Support before you continue.
QueryClients=127.0.0.1 AdminClients=127.0.0.1 IndexClients=127.0.0.1 |
3. In Windows Defender Firewall with Advanced Security, create an inbound rule that blocks TCP ports 9000, 9001, and 9002. To do this from an elevated PowerShell window, run:
New-NetFirewallRule -DisplayName "Block IDOL inbound" -Direction Inbound ` -Protocol TCP -LocalPort 9000,9001,9002 -Action Block |
4. Confirm that DocuShare search still returns results, then run the scan again.
| Important: If the IDOL search engine runs on a different server than DocuShare, do not block these ports. Instead, allow them only from the DocuShare server. |
If You Use a Scanner
Record the scanner finding, the port, the DocuShare release and patch level, and the search engine in use. Use the assessments above to decide whether a finding requires action in your configuration. A missing-header finding on port 9001 does not indicate that the search engine can be accessed from other systems.
How to Request Assistance
Contact Xerox DocuShare Support if the finding remains after you complete these steps. Provide the scanner finding, port, DocuShare release and patch level, search engine, operating system, and whether you use IIS. Do not send passwords.
Comments
0 comments
Article is closed for comments.