Skip to content

Conversation

@Jarrah-TLR
Copy link
Contributor

@Jarrah-TLR Jarrah-TLR commented Nov 11, 2025

There are some examples in the OSV database which have untyped references. Currently these fail to parse. For example: https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Debian%2FCVE-2018-11212.json?generation=1758701673567991&alt=media

I went for setting the ReferenceType to Undefined by default to retain backwards compatibility and avoid having to unwrap it every time. To me, Undefined doesn't feel particularly different to None.

There are some examples in the OSV database which have untyped
references and Severities. Currently these fail to parse. For example:
https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Debian%2FCVE-2018-11212.json?generation=1758701673567991&alt=media
Ubuntu keep adding items to their ecosystem strings, resulting in the
regex regularly failing and dropping all data. Instead, relax the regex
to allow it to parse only the start of the line. Having most of the data
is better than none. An example of this is "USN-7550-2.json".

Additionally, Ubuntu OSVs now include an ubuntu specific severity.
This otherwise matches the existing schema but is expected to contain a
simple string rather than the CVSS score. An example of this is
"UBUNTU-CVE-2025-9825.json".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant