CVE Tools
Sign in
Back to CVE-2016-3615

How to verify CVE-2016-3615

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 26 NVT checks for CVE-2016-3615. 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.120726' details='1'/>"
NVT OIDs (26)
  • 1.3.6.1.4.1.25623.1.0.120726since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.120727since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.703624since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.703632since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.808588since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.808595since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.842841since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.851429since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.851430since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.851505since 2026-06-25

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