You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the data quality issue observed
According to the CVE description the CVE is disputed, which is also shown by the tag "disputed" at MITRTE and therefore should have the "withdrawn"-field. At least you commented that the tag "disputed" at MITRE means "withdrawn" in osv.
Suggested changes to record
Add "withdrawn" to the entry.
The text was updated successfully, but these errors were encountered:
Please note that in OSV.dev, GHSA-4943-9vgg-gr5r and CVE-2021-3163 are different vulnerability records. In this particular instance, the former exists (and specifies the latter as an alias, and the latter does not exist).
GHSA-4943-9vgg-gr5r originates from the GitHub Advisory Database, and I am unsure of their treatment of records for disputed CVEs, but given I believe they human-review all advisories imported from the NVD, I would assume this is working as intended. GHSA-4943-9vgg-gr5r is the appropriate place to take this feedback.
The CVE ID
https://osv.dev/vulnerability/GHSA-4943-9vgg-gr5r
Describe the data quality issue observed
According to the CVE description the CVE is disputed, which is also shown by the tag "disputed" at MITRTE and therefore should have the "withdrawn"-field. At least you commented that the tag "disputed" at MITRE means "withdrawn" in osv.
Suggested changes to record
Add "withdrawn" to the entry.
The text was updated successfully, but these errors were encountered: