How to verify CVE-2017-16548

Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.

Verify with OpenVAS

Greenbone/OpenVAS ships 18 NVT checks for CVE-2017-16548. OpenVAS detects this CVE by NVT OID — enable the NVT in your scan config, or confirm it is in your feed with the query below.

Confirm the NVT is in your feed (GMP)

gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.704068' details='1'/>"

NVT OIDs (18)

1.3.6.1.4.1.25623.1.0.704068since 2026-06-25
1.3.6.1.4.1.25623.1.0.843758since 2026-06-25
1.3.6.1.4.1.25623.1.1.10.2017.0459since 2026-06-25
1.3.6.1.4.1.25623.1.1.1.1.2017.4068since 2026-06-25
1.3.6.1.4.1.25623.1.1.1.2.2017.1218since 2026-06-25
1.3.6.1.4.1.25623.1.1.12.2018.3543.1since 2026-06-25
1.3.6.1.4.1.25623.1.1.12.2018.3543.2since 2026-06-25
1.3.6.1.4.1.25623.1.1.13.2018.032.02since 2026-06-25
1.3.6.1.4.1.25623.1.1.17.1.2023.0067since 2026-06-25
1.3.6.1.4.1.25623.1.1.18.1.2024.11308.1since 2026-06-25

+ 8 more NVTs

New to OpenVAS? Greenbone documentation ↗

Confirmed exposed? That's one CVE on one host.

We check your whole external estate — hundreds of IPs and domains — for this and thousands more, on a schedule.

Scan my estate

Verify another CVE