Match each host and infrastructure vulnerability scenario to the underlying security weakness or misconfiguration it represents.
- An internal management host transmitting network monitoring telemetry using SNMPv1 across local subnets.Cleartext protocol exposure allowing management traffic interception.
- A third-party background service executable located in a directory with full write permissions assigned to non-administrative users.Weak file system permissions enabling local privilege escalation.
- An internal database server bound to a public interface without perimeter firewall rules or VLAN isolation.Improper network segmentation exposing internal database services.
- A legacy host operating system past end-of-life running unpatched network daemons with known exploit modules.Unsupported legacy software vulnerable to known remote exploits.
Answer
The scenarios match their respective security weaknesses as follows: SNMPv1 traffic matches cleartext protocol exposure; weak file permissions on executable directories match local privilege escalation risk; unsegmented database service exposure matches improper network segmentation; and unpatched end-of-life operating systems match unsupported legacy software vulnerability risk.
Each scenario maps directly to its specific vulnerability classification. SNMPv1 does not support encryption, exposing management strings in cleartext. Allowing standard users write access to service binary paths enables local file modification and privilege escalation. Exposing internal database ports directly without firewall or VLAN boundaries represents a breakdown in network segmentation. Continuing to host end-of-life operating systems exposes environments to known unpatched vulnerabilities.
Step-by-Step Solution
Key Concept
Host, Network, and Architecture Vulnerabilities