We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The data for GHSA-w9jx-4g6g-rp7x includes "type": 3 instead of "type": "CVSS_V4".
"type": 3
"type": "CVSS_V4"
To Reproduce Steps to reproduce the behaviour:
curl https://api.osv.dev/v1/vulns/GHSA-w9jx-4g6g-rp7x
Expected behaviour I'd expect the response to adhere to declared schema. So in this case it should show "type": "CVSS_V4".
Screenshots
Additional context I've come across this, because ORT started failing for TinyMCE and traced it back in ORT's code
The text was updated successfully, but these errors were encountered:
Attempt at updating the api_descriptor.pb proto (#2342)
e2601cd
Currently CVSS_4 is not correctly converted to JSON in the API. This is an attempt at fixing that issue (See #2331)
The API should now be correctly returning "type": "CVSS_V4" in these cases.
Thanks for reporting this! Let us know if you're still encountering this issue.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The data for GHSA-w9jx-4g6g-rp7x includes
"type": 3
instead of"type": "CVSS_V4"
.To Reproduce
Steps to reproduce the behaviour:
curl https://api.osv.dev/v1/vulns/GHSA-w9jx-4g6g-rp7x
Expected behaviour
I'd expect the response to adhere to declared schema. So in this case it should show
"type": "CVSS_V4"
.Screenshots
Additional context
I've come across this, because ORT started failing for TinyMCE and traced it back in ORT's code
The text was updated successfully, but these errors were encountered: