Will be updated only if there is an addition or modification to any vulnerability with a starting CVE® identifier After performingĪ one-time import of the complete data set using the compressed JSON vulnerability feeds, the "modified"Įach feed is updated nightly, but only if the content of that feed has changed. If you are locally mirroring NVD data, either the APIs or the data feeds may be used to stay synchronized. (except for the 2002 feeds which include vulnerabilities prior to and including "CVE-2002-"). The vulnerability feeds provide CVE® data organized by the first four digits of a CVE® identifier How to Keep Up-to-Date with the NVD Data Using the Traditional Feeds Reference data for common configuration items. The APIs are far more flexible and offer a richer dataset in a single interface compared to the JSON Vulnerability Feeds and CPE Match Feed.Įach vulnerability in the file includes a description and associated reference links from the CVE® dictionary feed, as well as CVSS base scores, vulnerable product configuration, and weakness categorization.Ī feed that provides the product/platform applicability statement to CPE URI matching based on the CPEs in the official CPE dictionary.Īn eight day window of security related software flaws.Ĭomments provided by vendors regarding a particular flaw affecting within a product.ĭictionary containing a list of products.Ĭommon Configuration Enumeration (CCE) Reference Data Users of the data feeds provided on this page must have an understanding of the XMLĪnd/or JSON standards and XML or JSON related technologies as defined byĪn alternative to the traditional vulnerability data feed files. Please read how to keep up-to-date with NVD data when using the traditional data feeds. The following table contains links and short descriptions for each API or data feed the NVD offers.
0 kommentar(er)
