VulDB is an open database which allows the edits from users all over the world. The edit of a single field is called a commit and introduces a wide variety of additional possibilities.
All edits are reviewed by selected moderators which allows us to guarantee the desired level of data quality and accuracy. A new commit might be processed like this:
- correct and can be validated ⇒ accepted and will be published to the official entry
- partially incorrect (e.g. wording, wrong data field selected) ⇒ corrected by a moderator
- could not be verified entierly ⇒ published with a low confidence score and/or addition comment
- is wrong (e.g. could not be verified, wrong data) ⇒ rejected with a comment
- is spam or profanity ⇒ values of offensive commits are set to invisible
VulDB is the only vulnerability database providing time variance. All commits are stored in the database and can be reviewed. This makes it possible to show commit histories and diffs of different versions of an entry. Vulnerability historians, investigating administrators and penetrations testers use this feature to understand the lifecycle of a vulnerability. It is possible to change the view during display of a vulnerability entry.
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!