Threat Surface Probe signature library

Runs in: Threat Surface Probe

The Threat Surface Probe detects CVEs that have a signature in its library. It runs on demand, and in scheduled reports at most once a day. It runs only against sites whose ownership your account has verified, because it sends test requests to your site rather than only reading public pages.

How it tests

  • The probe sends non-destructive test requests to your site that check whether a known flaw responds. It does not only read pages: many signatures send crafted requests that test for the flaw itself rather than reading a version number. This is why it runs only on verified sites.
  • Every scan runs four categories only: CVE detection, exposed panels, misconfigurations and default credentials. More intrusive categories are never run.
  • Before the signatures run, every scan runs two checks of our own on your site's response headers; one of them tests whether the software versions your site announces are current.
  • Your host name is resolved first; a host that resolves only to non-public addresses ends the run with that error. Every request, redirect hops and raw requests included, is then sent through a proxy that refuses any non-public address.
  • A CVE counts as covered when the library contains a signature for its CVE id in the CVE category.
  • You can scan only sites whose ownership your account has verified, and their subdomains.

What you see

  • A finding per matched signature, with its name and severity, streamed as the scan runs.
  • A scan with no signatures available is an error, never a clean result.
  • A timeout is reported as a timeout, and a scan failure with no output as an error, not as "nothing found".

Limits

  • The signatures are third-party. Many send crafted requests that test for the flaw rather than reading a version; this is why the probe requires ownership and runs in reports only for verified sites.
  • The signature library is refreshed daily.
  • A signature's quality is the library's; a CVE with a weak signature is covered only as well as that signature.

Rules this scan applies

Vulnerabilities this check covers 4,504

AdvisoryWhat it isSeverityRecords
CVE-2022-1020 —
CVE-2022-1013 —
CVE-2022-1007 —
CVE-2022-0968 —
CVE-2022-0963 —
CVE-2022-0954 —
CVE-2022-0952 —
CVE-2022-0949 —
CVE-2022-0948 —
CVE-2022-0928 —
CVE-2022-0899 —
CVE-2022-0885 —
CVE-2022-0879 —
CVE-2022-0873 —
CVE-2022-0870 —
CVE-2022-0869 —
CVE-2022-0867 —
CVE-2022-0864 —
CVE-2022-0846 —
CVE-2022-0827 —
CVE-2022-0826 —
CVE-2022-0824 —
CVE-2022-0817 —
CVE-2022-0814 —
CVE-2022-0788 —
CVE-2022-0787 —
CVE-2022-0786 —
CVE-2022-0785 —
CVE-2022-0784 —
CVE-2022-0783 —
CVE-2022-0781 —
CVE-2022-0776 —
CVE-2022-0773 —
CVE-2022-0769 —
CVE-2022-0765 —
CVE-2022-0760 —
CVE-2022-0747 —
CVE-2022-0735 —
CVE-2022-0693 —
CVE-2022-0692 —
CVE-2022-0679 —
CVE-2022-0678 —
CVE-2022-0666 —
CVE-2022-0660 —
CVE-2022-0658 —
CVE-2022-0656 —
CVE-2022-0653 —
CVE-2022-0651 —
CVE-2022-0599 —
CVE-2022-0597 —
CVE-2022-0595 —
CVE-2022-0594 —
CVE-2022-0592 —
CVE-2022-0591 —
CVE-2022-0540 —
CVE-2022-0535 —
CVE-2022-0533 —
CVE-2022-0482 —
CVE-2022-0479 —
CVE-2022-0441 —
CVE-2022-0439 —
CVE-2022-0437 —
CVE-2022-0434 —
CVE-2022-0432 —
CVE-2022-0429 —
CVE-2022-0424 —
CVE-2022-0422 —
CVE-2022-0415 —
CVE-2022-0412 —
CVE-2022-0381 —
CVE-2022-0378 —
CVE-2022-0349 —
CVE-2022-0346 —
CVE-2022-0342 —
CVE-2022-0288 —
CVE-2022-0281 —
CVE-2022-0271 —
CVE-2022-0250 —
CVE-2022-0234 —
CVE-2022-0228 —
CVE-2022-0220 —
CVE-2022-0218 —
CVE-2022-0212 —
CVE-2022-0208 —
CVE-2022-0206 —
CVE-2022-0201 —
CVE-2022-0189 —
CVE-2022-0188 —
CVE-2022-0169 —
CVE-2022-0165 —
CVE-2022-0150 —
CVE-2022-0149 —
CVE-2022-0148 —
CVE-2022-0147 —
CVE-2022-0140 —
CVE-2022-0087 —
CVE-2021-47795 —
CVE-2021-46704 —
CVE-2021-46424 —
CVE-2021-46422 —

Each advisory id links to its public record where one exists. This product uses data from the NVD API but is not endorsed or certified by the NVD.