VPN gateway runs a version with a known, published vulnerability
vpn.admin-soehne.example · port 443 (VPN gateway)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Description
The scan reported that the VPN gateway runs a firmware version named in a published security advisory from the vendor. The flaw lets someone on the internet stop the VPN service, without logging in, under certain conditions. The manual check confirmed the version with the client’s admin and that the vendor’s fix is not installed. The scan also reported an outdated SSH version on this host; the manual check showed the patches were in place, so that result was removed as a false positive.
Steps to reproduce
- Compare the firmware version the gateway reports with the vendor’s security advisory.
- Confirm the installed version and the missing fix with the client’s admin on the device.
- Check the gateway settings: the web portal option named in the advisory is switched on.
vpn.admin-soehne.example · port 443/tcp
Scan: firmware version listed in a published vendor advisory
Manual check: version confirmed on the device
Vendor fix: not installed
Web portal option: on Business impact
Until the fix is installed, an attacker could take the VPN offline, so remote staff and partners cannot work. Known flaws in VPN gateways are scanned for across the internet within days of an advisory, and cyber insurers ask about patch times for exactly these systems.
Remediation
Install the vendor’s fixed firmware version now, in a planned maintenance window. Switch off the web portal option if nobody needs it. Subscribe to the vendor’s security advisories and set a patch deadline for internet-facing systems, for example 7 days for serious flaws. The free re-scan then confirms the update.
CWE-1104 (Use of Unmaintained Third Party Components) · OWASP Top 10 2021: A06 Vulnerable and Outdated Components · BSI IT-Grundschutz OPS.1.1.3 (patch and change management)