CVE Tools
Sign in
Back to CVE-2020-1695

How to verify CVE-2020-1695

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 9 NVT checks for CVE-2020-1695. 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.878694' details='1'/>"
NVT OIDs (9)
  • 1.3.6.1.4.1.25623.1.0.878694since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.878695since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.10.2021.0039since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.11.2021.1775since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.12.2025.7351.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.12.2025.7630.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.14.2021.1775since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.16.2022.1483since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.8.2021.1775since 2026-06-25
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