How to verify CVE-2022-0175

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 11 NVT checks for CVE-2022-0175. 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.845262' details='1'/>"

NVT OIDs (11)

1.3.6.1.4.1.25623.1.0.845262since 2026-06-25
1.3.6.1.4.1.25623.1.0.854398since 2026-06-25
1.3.6.1.4.1.25623.1.1.10.2022.0401since 2026-06-25
1.3.6.1.4.1.25623.1.1.12.2022.5309.1since 2026-06-25
1.3.6.1.4.1.25623.1.1.16.2022.1776since 2026-06-25
1.3.6.1.4.1.25623.1.1.17.2024.0261since 2026-06-25
1.3.6.1.4.1.25623.1.1.17.2026.0255since 2026-07-30
1.3.6.1.4.1.25623.1.1.17.3.2026.0266since 2026-07-15
1.3.6.1.4.1.25623.1.1.18.1.2024.11770.1since 2026-06-25
1.3.6.1.4.1.25623.1.1.4.2022.0110.1since 2026-06-25

+ 1 more NVT

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