obdev CNA: CVE Report Card & Published CVEs

A CVE record only requires a description to be published. “Completeness” measures how often obdev also fills in the optional — but extremely useful — fields that make a vulnerability actually actionable: the affected vendor and product, a CVSS severity score, and a CWE weakness type. A higher score means more of this CNA’s CVEs include those details, so defenders spend less time enriching records by hand.

Report card grade

50%

Overall score

Overall completeness50%

Vendor completeness33.3%

Product completeness100%

CVSS completeness0%

CWE completeness66.7%

100%

Update rate

Records revised after publishing

Vendor diversity

Distinct vendors covered

337 chars

Avg description length

Per CVE record

2016-11-15

First CVE date

Earliest assignment

2020-06-30

Latest CVE date

Most recent assignment

N/A

Average CVSS

Across scored CVEs

What these scores mean

Vendor completeness: The share of this CNA's CVEs that name an affected vendor.
Product completeness: The share that name a specific affected product.
CVSS completeness: The share that include a CVSS severity score.
CWE completeness: The share mapped to a CWE weakness type.
Update rate: How often this CNA revises CVE records after first publishing them.
Vendor diversity: How many distinct vendors this CNA publishes CVEs for.

What these scores mean

obdev

Overview

Data quality report card

What these scores mean

Common weakness types

Publishing activity by year

Top vendors

Top products

Latest CVEs

Other CNAs

Frequently asked questions

What is the obdev CNA?

How many CVEs has obdev published?

What is obdev's CVE data quality grade?

What products does obdev publish CVEs for?

Which vendors does obdev cover?

Is obdev actively publishing CVEs?

Are any of obdev's CVEs in CISA's Known Exploited Vulnerabilities catalog?

What are the most common weakness types in obdev's CVEs?

How does obdev rank among CNAs?

References

Track obdev CVEs