Closed jcran closed 4 years ago
Note that this is integrated by default and there may need to be some additional normalization of fingerprints in the future. See below for an example - Recog checks are called out in the match details:
Fingerprint:
- Cloudflare Cloudflare - cloudflare cookie (CPE: cpe:2.3:s:cloudflare:cloudflare::) (Tags: ["CDN", "WAF"]) (Hide: false)
- Cloudflare Cloudflare - header (CPE: cpe:2.3:s:cloudflare:cloudflare::) (Tags: ["CDN", "WAF"]) (Hide: false)
- Cloudflare Cloudflare - server header (CPE: cpe:2.3:s:cloudflare:cloudflare::) (Tags: ["CDN", "WAF"]) (Hide: false)
- Cloudflare Cloudflare - ct header pointed to cloudflare (CPE: cpe:2.3:s:cloudflare:cloudflare::) (Tags: ["CDN", "WAF"]) (Hide: false)
- Webflow Webflow - body string (CPE: cpe:2.3:s:webflow:webflow::) (Tags: ["CMS", "SaaS"]) (Hide: false)
- CloudFlare CloudFlare Load Balancer - CloudFlare web load balancer endpoint (Recog: http_header.server) (CPE: ) (Tags: ) (Hide: false)
Integrates and runs Rapid7's pattern matching lib "Recog" (https://github.com/rapid7/recog) as part of the normal Ident run. Only HTTP Cookies and Server Headers are currently supported, but this lays the groundwork to support other network services - which is where the true benefit is.
An example, requesting a page and returning the fingerprints. Considered keeping the results separate but having them under the returned 'fingerprint' attribute can give us vulnerability version based inference with no additional work - provided the checks are specific enough and handle backporting (which is a tall order). We shall see.