2023-04-27 15:02:47 +02:00
# nvd-json-data-feeds
2023-04-24 14:55:30 +02:00
Community reconstruction of the soon-to-be deprecated JSON NVD Data Feeds.
2023-05-17 08:57:59 +00:00
[Releases ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest ) each day at 00:00 AM UTC.
2023-04-27 16:00:24 +02:00
Repository synchronizes with the NVD every 2 hours.
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
## Repository at a Glance
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
### Last Repository Update
2023-04-24 14:55:30 +02:00
```plain
2023-06-21 22:00:32 +00:00
2023-06-21T22:00:29.200365+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Most recent CVE Modification Timestamp synchronized with NVD
2023-04-24 14:55:30 +02:00
```plain
2023-06-21 22:00:32 +00:00
2023-06-21T21:15:11.357000+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Last Data Feed Release
2023-04-24 14:55:30 +02:00
2023-05-17 08:57:59 +00:00
Download and Changelog: [Click ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest )
2023-04-24 14:55:30 +02:00
```plain
2023-06-21 02:00:31 +00:00
2023-06-21T00:00:13.655453+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Total Number of included CVEs
2023-04-24 14:55:30 +02:00
2023-04-27 15:02:47 +02:00
```plain
2023-06-21 22:00:32 +00:00
218201
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### CVEs added in the last Commit
2023-04-24 14:55:30 +02:00
2023-06-21 22:00:32 +00:00
Recently added CVEs: `10`
2023-06-20 18:00:42 +00:00
2023-06-21 22:00:32 +00:00
* [CVE-2023-0969 ](CVE-2023/CVE-2023-09xx/CVE-2023-0969.json ) (`2023-06-21T20:15:09.660` )
* [CVE-2023-0970 ](CVE-2023/CVE-2023-09xx/CVE-2023-0970.json ) (`2023-06-21T20:15:09.843` )
* [CVE-2023-0971 ](CVE-2023/CVE-2023-09xx/CVE-2023-0971.json ) (`2023-06-21T20:15:09.943` )
* [CVE-2023-0972 ](CVE-2023/CVE-2023-09xx/CVE-2023-0972.json ) (`2023-06-21T20:15:10.023` )
* [CVE-2023-25435 ](CVE-2023/CVE-2023-254xx/CVE-2023-25435.json ) (`2023-06-21T20:15:10.100` )
* [CVE-2023-33289 ](CVE-2023/CVE-2023-332xx/CVE-2023-33289.json ) (`2023-06-21T20:15:10.157` )
* [CVE-2023-33591 ](CVE-2023/CVE-2023-335xx/CVE-2023-33591.json ) (`2023-06-21T20:15:10.213` )
* [CVE-2023-3110 ](CVE-2023/CVE-2023-31xx/CVE-2023-3110.json ) (`2023-06-21T20:15:10.263` )
* [CVE-2023-24261 ](CVE-2023/CVE-2023-242xx/CVE-2023-24261.json ) (`2023-06-21T21:15:10.867` )
* [CVE-2023-33405 ](CVE-2023/CVE-2023-334xx/CVE-2023-33405.json ) (`2023-06-21T21:15:11.357` )
2023-06-02 18:00:31 +00:00
2023-06-09 22:00:29 +00:00
2023-06-14 14:00:29 +00:00
### CVEs modified in the last Commit
2023-06-14 06:00:29 +00:00
2023-06-21 22:00:32 +00:00
Recently modified CVEs: `40`
* [CVE-2023-24937 ](CVE-2023/CVE-2023-249xx/CVE-2023-24937.json ) (`2023-06-21T20:51:00.080` )
* [CVE-2023-28598 ](CVE-2023/CVE-2023-285xx/CVE-2023-28598.json ) (`2023-06-21T20:51:49.067` )
* [CVE-2023-3236 ](CVE-2023/CVE-2023-32xx/CVE-2023-3236.json ) (`2023-06-21T20:52:15.233` )
* [CVE-2023-28599 ](CVE-2023/CVE-2023-285xx/CVE-2023-28599.json ) (`2023-06-21T20:52:21.747` )
* [CVE-2023-28600 ](CVE-2023/CVE-2023-286xx/CVE-2023-28600.json ) (`2023-06-21T20:52:50.547` )
* [CVE-2023-28601 ](CVE-2023/CVE-2023-286xx/CVE-2023-28601.json ) (`2023-06-21T20:53:18.250` )
* [CVE-2023-28602 ](CVE-2023/CVE-2023-286xx/CVE-2023-28602.json ) (`2023-06-21T20:53:37.857` )
* [CVE-2023-28603 ](CVE-2023/CVE-2023-286xx/CVE-2023-28603.json ) (`2023-06-21T20:53:55.603` )
* [CVE-2023-3235 ](CVE-2023/CVE-2023-32xx/CVE-2023-3235.json ) (`2023-06-21T20:54:16.250` )
* [CVE-2023-34113 ](CVE-2023/CVE-2023-341xx/CVE-2023-34113.json ) (`2023-06-21T20:54:16.867` )
* [CVE-2023-34120 ](CVE-2023/CVE-2023-341xx/CVE-2023-34120.json ) (`2023-06-21T20:54:35.730` )
* [CVE-2023-34121 ](CVE-2023/CVE-2023-341xx/CVE-2023-34121.json ) (`2023-06-21T20:54:52.100` )
* [CVE-2023-34122 ](CVE-2023/CVE-2023-341xx/CVE-2023-34122.json ) (`2023-06-21T20:55:04.803` )
* [CVE-2023-34114 ](CVE-2023/CVE-2023-341xx/CVE-2023-34114.json ) (`2023-06-21T21:02:32.257` )
* [CVE-2023-27836 ](CVE-2023/CVE-2023-278xx/CVE-2023-27836.json ) (`2023-06-21T21:02:52.600` )
* [CVE-2023-2570 ](CVE-2023/CVE-2023-25xx/CVE-2023-2570.json ) (`2023-06-21T21:03:56.260` )
* [CVE-2023-30631 ](CVE-2023/CVE-2023-306xx/CVE-2023-30631.json ) (`2023-06-21T21:05:24.670` )
* [CVE-2023-33933 ](CVE-2023/CVE-2023-339xx/CVE-2023-33933.json ) (`2023-06-21T21:05:39.700` )
* [CVE-2023-34000 ](CVE-2023/CVE-2023-340xx/CVE-2023-34000.json ) (`2023-06-21T21:06:14.600` )
* [CVE-2023-34149 ](CVE-2023/CVE-2023-341xx/CVE-2023-34149.json ) (`2023-06-21T21:06:26.343` )
* [CVE-2023-34396 ](CVE-2023/CVE-2023-343xx/CVE-2023-34396.json ) (`2023-06-21T21:06:39.670` )
* [CVE-2023-3001 ](CVE-2023/CVE-2023-30xx/CVE-2023-3001.json ) (`2023-06-21T21:06:51.690` )
* [CVE-2023-2828 ](CVE-2023/CVE-2023-28xx/CVE-2023-2828.json ) (`2023-06-21T21:15:11.027` )
* [CVE-2023-2911 ](CVE-2023/CVE-2023-29xx/CVE-2023-2911.json ) (`2023-06-21T21:15:11.177` )
* [CVE-2023-31975 ](CVE-2023/CVE-2023-319xx/CVE-2023-31975.json ) (`2023-06-21T21:15:11.250` )
2023-04-24 14:55:30 +02:00
## Download and Usage
There are several ways you can work with the data in this repository:
### 1) Release Data Feed Packages
2023-05-24 12:00:30 +00:00
The most straightforward approach is to obtain the latest Data Feed release packages [here ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest ).
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
Each day at 00:00 AM UTC we package and upload JSON files that aim to reconstruct the legacy NVD CVE Data Feeds.
2023-04-24 14:55:30 +02:00
Those are aggregated by the `year` part of the CVE identifier:
```
# CVE-<YEAR>.json
CVE-1999.json
CVE-2001.json
CVE-2002.json
CVE-2003.json
[...]
CVE-2023.json
```
2023-04-27 15:02:47 +02:00
We also upload the well-known `Recent` and `Modified` feeds.
Furthermore, we provide the `All` feed, which contains a recent snapshot of all NVD records.
2023-04-27 16:00:24 +02:00
Once your local copy is synchronized and the last synchronization is no older than 8 days, you can rely on these to stay up to date:
2023-04-24 14:55:30 +02:00
```plain
CVE-Recent.json # CVEs that were added in the previous eight days
CVE-Modified.json # CVEs that were modified or added in the previous eight days
```
2023-04-27 16:00:24 +02:00
Note that all feeds are distributed in `xz` -compressed format to save storage and bandwidth.
2023-04-24 14:55:30 +02:00
For decompression execute:
```sh
xz -d -k < feed > .json.xz
```
#### Automation using Release Data Feed Packages
2023-04-27 16:00:24 +02:00
You can fetch the latest releases for each package with the following static link layout:
2023-04-24 14:55:30 +02:00
```sh
2023-04-27 15:02:47 +02:00
https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-< YEAR > .json.xz
2023-04-24 14:55:30 +02:00
```
Example:
```sh
2023-04-27 15:02:47 +02:00
wget https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-2023.json.xz
2023-04-24 14:55:30 +02:00
xz -d -k CVE-2023.json.xz
```
2023-04-27 16:00:24 +02:00
### 2) Clone the Repository (with Git History)
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
As you can see by browsing this repository, there is a slight difference between the release packages format and the repository folder structure.
2023-04-24 14:55:30 +02:00
This is because we want to maintain explorability of the dataset.
2023-04-27 16:00:24 +02:00
Each CVE gets its own JSON file, e.g., `CVE-1999-0001.json` .
2023-04-24 14:55:30 +02:00
Here, each file is put into a folder layout that first sorts by CVE `year` identifier part and then by `number` part.
2023-04-27 16:00:24 +02:00
We mask (`xx` ) the last two digits to create easily navigable folders that hold a maximum of 100 CVE JSON files:
2023-04-24 14:55:30 +02:00
```plain
.
├── CVE-1999
│ ├── CVE-1999-00xx
│ │ ├── CVE-1999-0001.json
│ │ ├── CVE-1999-0002.json
│ │ └── [...]
│ ├── CVE-1999-01xx
2023-04-25 17:08:25 +02:00
│ │ ├── CVE-1999-0101.json
│ │ └── [...]
2023-04-24 14:55:30 +02:00
│ └── [...]
├── CVE-2000
│ ├── CVE-2000-00xx
│ ├── CVE-2000-01xx
│ └── [...]
└── [...]
```
2023-04-27 16:00:24 +02:00
A byproduct of managing and continuously updating this dataset via Git is that we can track changes over time through the Git history.
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
If you are interested in having the NVD data as organized above, including the historical data of changes, just clone this repository (large!):
2023-04-24 14:55:30 +02:00
```sh
2023-04-27 15:02:47 +02:00
git clone https://github.com/fkie-cad/nvd-json-data-feeds.git
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### 3) Clone the Repository (without Git History)
2023-04-24 14:55:30 +02:00
Don't need the history? Then create a shallow copy:
```sh
2023-04-27 15:02:47 +02:00
git clone --depth 1 -b main https://github.com/fkie-cad/nvd-json-data-feeds.git
2023-04-24 14:55:30 +02:00
```
## Motivation
2023-04-27 16:00:24 +02:00
As of September 2023, the NIST will retire all [JSON-based NVD Data Feeds ](https://nvd.nist.gov/vuln/data-feeds#divRetirementBanner-1 ).
2023-04-24 14:55:30 +02:00
The new [NVD CVE API 2.0 ](https://nvd.nist.gov/developers/vulnerabilities ) is, without a doubt, a great way to obtain CVE information.
However, we from [Fraunhofer FKIE - Cyber Analysis and Defense ](https://www.fkie.fraunhofer.de/en/departments/cad.html ) believe that the API does not cover a variety of use cases.
The legacy NVD Data Feeds provided a convenient way to quickly obtain a complete, file-based offline database snapshot; just download the `CVE-<YEAR>.tar.gz` , decompress it, and use it as you please, e.g.:
2023-04-27 16:00:24 +02:00
* Put the JSON feed into a document-based database and quickly leverage upon that data in your software project, ...
2023-04-24 14:55:30 +02:00
* Parse and analyze it using your favorite programming language, ...
* Put it on a USB stick and transfer it to a system without internet access, or ...
* Query the file using `jq` !
2023-04-27 16:00:24 +02:00
Unfortunately, the new NVD API 2.0 adds complexity to this process.
2023-04-24 14:55:30 +02:00
We want to preserve ease of use by reconstructing these data sources.
## Non-Endorsement Clause
This project uses and redistributes data from the NVD API but is not endorsed or certified by the NVD.