-
I have used the API for some time now, but today I got an error from the server.
You can reproduce the issue with the following command:
`curl -X GET https://api.msrc.microsoft.com/cvrf/2020-mar?api…
-
# Feature request
### What new feature do you want?
An additional column 'epoch' in the rpm_packages schema, which holds information about the [rpm package epoch number](http://ftp.rpm.o…
-
Hi MSRC team,
Is the API currently down? I just test the API and it is returning Internal Server Error 500.
Is there any maintenance running?
url: https://api.msrc.microsoft.com/cvrf/2020-jul?api-…
-
The object "product_status" should have a least one property as stated in the specification of CVRF 1.2 (see CSAF-6.10-1).
-
The field "type" in items of the array "remediations" should be required as stated in the specification of CVRF 1.2 (see https://docs.oasis-open.org/csaf/csaf-cvrf/v1.2/cs01/csaf-cvrf-v1.2-cs01.html#…
-
Have also been using the API's for a while now, however today (8/7/2020) I have been getting 500 HTTP codes back. Haven't changed my apikey and can't seem to understand what's wrong.
-
- Is this an issue with SCAP Workbench?
No
- Is this an issue with SCAP Security Guide (i.e., related to the content of scans, not the scanner proper)?
-I don't think so
- Is this an issue…
-
The current version of the CSAF CVRF parser supports CVRF 1.2 (XML) only. It does not support the CSAF 2.0 JSON draft schema. This should be reflected in the README.md documentation.
-
It would be nice to see https://cve.mitre.org/ as vuln source
-
https://www.suse.com/support/security/cvrf/