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 bug
Even though the vulnerability is in "Final" state, affected software versions are not shown via API. But it is shown in the regular Cisco Security Advisory page.
API representation: curl -X GET -H "Accept: application/json" -H "Authorization: Bearer <removed>" 'https://apix.cisco.com/security/advisories/v2/advisory/cisco-sa-http2-reset-d8Kf32vZ'
Expected behavior
Show at least the same affected product information (including affected/fixed versions) via API as in the CiscoSecurityAdvisory page.
Screenshots
Web page data with affected products + fixed versions:
API response with affected products:
Additional context
Seems that the proccess of syncing the affected version data is not prioritized for the openVulnAPI backend, which is a shame.
For this product to be usable it should be up to date and considered reliable.
The text was updated successfully, but these errors were encountered:
Describe the bug
Even though the vulnerability is in "Final" state, affected software versions are not shown via API. But it is shown in the regular Cisco Security Advisory page.
To Reproduce
Official page describing vulnerability:
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-http2-reset-d8Kf32vZ
API representation:
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer <removed>" 'https://apix.cisco.com/security/advisories/v2/advisory/cisco-sa-http2-reset-d8Kf32vZ'
Expected behavior
Show at least the same affected product information (including affected/fixed versions) via API as in the CiscoSecurityAdvisory page.
Screenshots
Web page data with affected products + fixed versions:
API response with affected products:
Additional context
Seems that the proccess of syncing the affected version data is not prioritized for the openVulnAPI backend, which is a shame.
For this product to be usable it should be up to date and considered reliable.
The text was updated successfully, but these errors were encountered: