CVE Tools
Back to CVE-2015-3225

How to verify CVE-2015-3225

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 27 NVT checks for CVE-2015-3225. 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.160657' details='1'/>"
NVT OIDs (27)
  • 1.3.6.1.4.1.25623.1.0.160657since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.703322since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.869892since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.869908since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.10.2015.0346since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.1.2015.3322since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.2.2015.254since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.18.1.2024.10406.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.18.1.2024.11344.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.18.1.2024.11345.1since 2026-06-25

+ 17 more NVTs

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