CVE Tools
Sign in
Back to CVE-2023-5679

How to verify CVE-2023-5679

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 47 NVT checks for CVE-2023-5679. 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.114426' details='1'/>"
NVT OIDs (47)
  • 1.3.6.1.4.1.25623.1.0.114426since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.151723since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.151724since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.153749since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.833249since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.833804since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.885732since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.885738since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.885810since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.885812since 2026-06-25

+ 37 more NVTs

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