A security analyst conducts an audit of an internal management server and inspects the following listening socket bindings and active process report:
Proto Local Address Foreign Address State PID/Program name
tcp 0.0.0.0:21 0.0.0.0:* LISTEN 812/vsftpd
tcp 0.0.0.0:5900 0.0.0.0:* LISTEN 1044/vncserver
tcp 127.0.0.1:9090 0.0.0.0:* LISTEN 1120/cockpit-daemon
Further investigation confirms that `vncserver` is configured without password authentication and accepts connections from any source IP. Which of the following represents the primary root cause host and architecture vulnerability in this deployment?
- Insecure service configuration allowing unauthenticated binding to wildcard network interfacesAnswer
- BOver-reliance on perimeter firewalls to protect unauthenticated internal management services
- CFailure to apply network-level packet filtering firewalls to mitigate software memory corruption vulnerabilities
- DMisclassification of remote management software as a detective security control rather than a preventive control
Answer
Insecure service configuration allowing unauthenticated binding to wildcard network interfaces
The socket audit shows VNC bound to `0.0.0.0:5900`, exposing the service across all network interfaces. Combined with disabled authentication, any internal network host can establish a remote desktop session. The root vulnerability is the insecure host service configuration.
Step-by-Step Solution
Key Concept
Host and Architecture Vulnerabilities - Insecure Service Configuration and Network Socket Exposure