Skip to main content
Private access is opening up — request an invite
askFinz
All collections
Reference collection

Software vulnerabilities, as disclosed

Disclosed weaknesses in software and the systems built on it, held as records — the disclosure itself, not the coverage of it.

225kdisclosures
severity declared
4
per record
2.1 KB

How it divides

1 dimension · press a band to read it
Severity · declared186,605 of 224,848 declared · 83.0%
  • Medium84,078 · 45.1%
  • High77,865 · 41.7%
  • Critical16,568 · 8.9%
  • Low8,094 · 4.3%
readout

84,078 disclosures are filed under Medium — 45.1% of those that declare it.

186,605 of 224,848 declared · 83.0%. The rest carry no value for this field, so these shares are of the declared set and do not add up to the collection.

What you can do with it

Search by what is affected — Describe the component or the behaviour in plain words and reach the disclosures that concern it.

Read it beside the code — Repositories and developer discussion sit on neighbouring shelves, so a disclosure and its context arrive together.

Follow it back — Every record keeps the address it was read from, so a disclosure can be checked where it was made.

Read by

Code
code.askfinz.ai

Where it stops

It is not a scanner and it is not an alerting service. Finding a disclosure is not being told that you are exposed to it.

A disclosure is what was published. Whether it applies to your version, your configuration or your deployment is a separate judgement.

All collectionsHow the index worksThe web index
Software vulnerability (CVE) search — askFinz