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-2012-4547 —
CVE-2012-4273 —
CVE-2012-4253 —
CVE-2012-4242 —
CVE-2012-4032 —
CVE-2012-3153 —
CVE-2012-2371 —
CVE-2012-1835 —
CVE-2012-1823 CISA KEV PHP-CGI Query String Parameter Vulnerability exploited
CVE-2012-1226 —
CVE-2012-10018 —
CVE-2012-0996 —
CVE-2012-0991 —
CVE-2012-0981 —
CVE-2012-0901 —
CVE-2012-0896 —
CVE-2012-0394 —
CVE-2012-0392 —
CVE-2011-5265 —
CVE-2011-5252 —
CVE-2011-5181 —
CVE-2011-5179 —
CVE-2011-5107 —
CVE-2011-5106 —
CVE-2011-4926 —
CVE-2011-4804 —
CVE-2011-4640 —
CVE-2011-4624 —
CVE-2011-4618 —
CVE-2011-4336 —
CVE-2011-3600 —
CVE-2011-3315 —
CVE-2011-2780 —
CVE-2011-2744 —
CVE-2011-1669 —
CVE-2011-0518 —
CVE-2011-0049 —
CVE-2010-5286 —
CVE-2010-5278 —
CVE-2010-5028 —
CVE-2010-4977 —
CVE-2010-4769 —
CVE-2010-4719 —
CVE-2010-4617 —
CVE-2010-4282 —
CVE-2010-4239 —
CVE-2010-4231 —
CVE-2010-3426 —
CVE-2010-3203 —
CVE-2010-2920 —
CVE-2010-2918 —
CVE-2010-2861 CISA KEV Adobe ColdFusion Directory Traversal Vulnerability exploited
CVE-2010-2857 —
CVE-2010-2682 —
CVE-2010-2680 —
CVE-2010-2507 —
CVE-2010-2307 —
CVE-2010-2259 —
CVE-2010-2128 —
CVE-2010-2122 —
CVE-2010-2050 —
CVE-2010-2045 —
CVE-2010-2037 —
CVE-2010-2036 —
CVE-2010-2035 —
CVE-2010-2034 —
CVE-2010-2033 —
CVE-2010-2018 —
CVE-2010-1983 —
CVE-2010-1982 —
CVE-2010-1981 —
CVE-2010-1980 —
CVE-2010-1979 —
CVE-2010-1977 —
CVE-2010-1957 —
CVE-2010-1956 —
CVE-2010-1955 —
CVE-2010-1954 —
CVE-2010-1953 —
CVE-2010-1952 —
CVE-2010-1878 —
CVE-2010-1875 —
CVE-2010-1870 —
CVE-2010-1858 —
CVE-2010-1723 —
CVE-2010-1722 —
CVE-2010-1719 —
CVE-2010-1718 —
CVE-2010-1717 —
CVE-2010-1715 —
CVE-2010-1714 —
CVE-2010-1659 —
CVE-2010-1658 —
CVE-2010-1657 —
CVE-2010-1653 —
CVE-2010-1607 —
CVE-2010-1603 —
CVE-2010-1602 —
CVE-2010-1601 —
CVE-2010-1586 —

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.