How to verify CVE-2017-5645
Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.
How to verify this vulnerability
Scanner data tells you how to confirm whether your systems are actually affected — not just that the CVE exists. Run a Nuclei template against your target for a yes/no answer in seconds.
nuclei -id CVE-2017-5645 -u your-target:port -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- criticalOfficialtcpApache Log4j Server - Deserialization Command ExecutionGitHub ↗
- criticalCommunitytcpApache Log4j Server - Deserialization Command ExecutionGitHub ↗
Find every CVE you can verify
Search the whole database by Nuclei coverage — filter by vendor, severity and KEV to build a verification list for your entire stack.
- Filter all CVEs that ship a Nuclei template
- Combine with vendor, severity & KEV
- Build a scan list across your stack
This template is on GitHub already — an account lets you search and filter every CVE that has one, not just this CVE.
Verify with OpenVAS
Greenbone/OpenVAS ships 28 NVT checks for CVE-2017-5645. 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.
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.117861' details='1'/>"1.3.6.1.4.1.25623.1.0.117861since 2026-06-251.3.6.1.4.1.25623.1.0.117862since 2026-06-251.3.6.1.4.1.25623.1.0.140682since 2026-06-251.3.6.1.4.1.25623.1.0.143546since 2026-06-251.3.6.1.4.1.25623.1.0.143708since 2026-06-251.3.6.1.4.1.25623.1.0.143709since 2026-06-251.3.6.1.4.1.25623.1.0.143710since 2026-06-251.3.6.1.4.1.25623.1.0.144295since 2026-06-251.3.6.1.4.1.25623.1.0.144296since 2026-06-251.3.6.1.4.1.25623.1.0.144297since 2026-06-25
+ 18 more NVTs