CVE Tools
Back to CVE-2022-21724

How to verify CVE-2022-21724

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 13 NVT checks for CVE-2022-21724. 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.149480' details='1'/>"
NVT OIDs (13)
  • 1.3.6.1.4.1.25623.1.0.149480since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.149999since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.171312since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.705196since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.820261since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.893018since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.1.2022.5196since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.1.2.2022.3018since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.16.2022.1535since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.17.3.2025.0130since 2026-06-25

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