CVE Census

About

One place for the whole life of every CVE

Data about vulnerabilities is public but scattered. The CVE Program publishes records; NIST analyses some of them; CISA, ENISA and others list the ones being exploited; FIRST predicts which will be; Exploit-DB, Metasploit and GitHub hold the exploits; OSV and the Linux distributions hold the fixes; papers and bug-bounty platforms hold the research. Each answers one question well.

The CVE Census reads all of them every day and joins them on the CVE ID, so one record follows a vulnerability from the day its ID is reserved to the day it is exploited or fixed. That makes questions answerable that no single source can: how long exploitation takes after disclosure, how often attackers move without any public exploit, whether the scores used to decide what to patch first point at what is later exploited, whose records are complete, who finds the bugs.

It is built like the Swiss Security Census: collected on a schedule, published as a static site, with the method written down and the data open. The idea of asking hard questions of vulnerability data owes a lot to Jerry Gamblin's RogoLabs, whose CNA Scorecard data appears on CNA pages for comparison.

Who

A project of Webcracy.ch by Liam Giannini. Contact: contact@webcracy.ch.

Not affiliated

The census is independent. It is not affiliated with or endorsed by the CVE Program, MITRE, NIST, CISA, ENISA, FIRST, Google, Rapid7, OffSec, ProjectDiscovery, Trend Micro, HackerOne, GitHub or any other source. CVE® is a registered trademark of The MITRE Corporation.