CVE Tools
Sign in
Back to CVE-2017-16227

How to verify CVE-2017-16227

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 17 NVT checks for CVE-2017-16227. 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.140461' details='1'/>"
NVT OIDs (17)
  • 1.3.6.1.4.1.25623.1.0.140461since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.704011since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.843355since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.851705since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.873832since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.873841since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.10.2017.0416since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.1.2017.4011since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.2.2017.1152since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.12.2017.3471.1since 2026-06-25

+ 7 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