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-07-17 18:00:48 +00:00
2023-07-17T18:00:44.570487+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-07-17 18:00:48 +00:00
2023-07-17T18:00:01.033000+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-07-17 02:00:54 +00:00
2023-07-17T00:00:13.572791+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-07-17 18:00:48 +00:00
220462
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-07-17 18:00:48 +00:00
Recently added CVEs: `23`
* [CVE-2021-37386 ](CVE-2021/CVE-2021-373xx/CVE-2021-37386.json ) (`2023-07-17T17:15:09.377` )
* [CVE-2022-36424 ](CVE-2022/CVE-2022-364xx/CVE-2022-36424.json ) (`2023-07-17T16:15:09.583` )
* [CVE-2022-38062 ](CVE-2022/CVE-2022-380xx/CVE-2022-38062.json ) (`2023-07-17T16:15:09.673` )
* [CVE-2023-35818 ](CVE-2023/CVE-2023-358xx/CVE-2023-35818.json ) (`2023-07-17T16:15:09.940` )
* [CVE-2023-36656 ](CVE-2023/CVE-2023-366xx/CVE-2023-36656.json ) (`2023-07-17T16:15:09.987` )
* [CVE-2023-37974 ](CVE-2023/CVE-2023-379xx/CVE-2023-37974.json ) (`2023-07-17T16:15:10.037` )
* [CVE-2023-37985 ](CVE-2023/CVE-2023-379xx/CVE-2023-37985.json ) (`2023-07-17T16:15:10.107` )
* [CVE-2023-3577 ](CVE-2023/CVE-2023-35xx/CVE-2023-3577.json ) (`2023-07-17T16:15:10.330` )
* [CVE-2023-3581 ](CVE-2023/CVE-2023-35xx/CVE-2023-3581.json ) (`2023-07-17T16:15:10.410` )
* [CVE-2023-3582 ](CVE-2023/CVE-2023-35xx/CVE-2023-3582.json ) (`2023-07-17T16:15:10.487` )
* [CVE-2023-3584 ](CVE-2023/CVE-2023-35xx/CVE-2023-3584.json ) (`2023-07-17T16:15:10.553` )
* [CVE-2023-3585 ](CVE-2023/CVE-2023-35xx/CVE-2023-3585.json ) (`2023-07-17T16:15:10.633` )
* [CVE-2023-3586 ](CVE-2023/CVE-2023-35xx/CVE-2023-3586.json ) (`2023-07-17T16:15:10.707` )
* [CVE-2023-3587 ](CVE-2023/CVE-2023-35xx/CVE-2023-3587.json ) (`2023-07-17T16:15:10.780` )
* [CVE-2023-3590 ](CVE-2023/CVE-2023-35xx/CVE-2023-3590.json ) (`2023-07-17T16:15:10.857` )
* [CVE-2023-3591 ](CVE-2023/CVE-2023-35xx/CVE-2023-3591.json ) (`2023-07-17T16:15:10.933` )
* [CVE-2023-3593 ](CVE-2023/CVE-2023-35xx/CVE-2023-3593.json ) (`2023-07-17T16:15:11.037` )
* [CVE-2023-3613 ](CVE-2023/CVE-2023-36xx/CVE-2023-3613.json ) (`2023-07-17T16:15:11.107` )
* [CVE-2023-3614 ](CVE-2023/CVE-2023-36xx/CVE-2023-3614.json ) (`2023-07-17T16:15:11.173` )
* [CVE-2023-3615 ](CVE-2023/CVE-2023-36xx/CVE-2023-3615.json ) (`2023-07-17T16:15:11.237` )
* [CVE-2023-28767 ](CVE-2023/CVE-2023-287xx/CVE-2023-28767.json ) (`2023-07-17T17:15:09.883` )
* [CVE-2023-34669 ](CVE-2023/CVE-2023-346xx/CVE-2023-34669.json ) (`2023-07-17T17:15:09.993` )
* [CVE-2023-37475 ](CVE-2023/CVE-2023-374xx/CVE-2023-37475.json ) (`2023-07-17T17:15:10.127` )
2023-07-01 02:00:32 +00:00
2023-07-04 02:00:31 +00:00
2023-07-06 06:00:29 +00:00
### CVEs modified in the last Commit
2023-07-06 04:00:49 +00:00
2023-07-17 18:00:48 +00:00
Recently modified CVEs: `23`
* [CVE-2019-1937 ](CVE-2019/CVE-2019-19xx/CVE-2019-1937.json ) (`2023-07-17T17:15:09.210` )
* [CVE-2022-24715 ](CVE-2022/CVE-2022-247xx/CVE-2022-24715.json ) (`2023-07-17T17:15:09.443` )
* [CVE-2022-36354 ](CVE-2022/CVE-2022-363xx/CVE-2022-36354.json ) (`2023-07-17T17:15:09.560` )
* [CVE-2022-41981 ](CVE-2022/CVE-2022-419xx/CVE-2022-41981.json ) (`2023-07-17T17:15:09.703` )
* [CVE-2022-47172 ](CVE-2022/CVE-2022-471xx/CVE-2022-47172.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2022-4361 ](CVE-2022/CVE-2022-43xx/CVE-2022-4361.json ) (`2023-07-17T17:50:07.437` )
* [CVE-2023-0026 ](CVE-2023/CVE-2023-00xx/CVE-2023-0026.json ) (`2023-07-17T16:15:09.753` )
* [CVE-2023-3217 ](CVE-2023/CVE-2023-32xx/CVE-2023-3217.json ) (`2023-07-17T16:15:10.247` )
* [CVE-2023-37269 ](CVE-2023/CVE-2023-372xx/CVE-2023-37269.json ) (`2023-07-17T17:15:10.040` )
* [CVE-2023-2495 ](CVE-2023/CVE-2023-24xx/CVE-2023-2495.json ) (`2023-07-17T17:31:26.053` )
* [CVE-2023-2958 ](CVE-2023/CVE-2023-29xx/CVE-2023-2958.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-31851 ](CVE-2023/CVE-2023-318xx/CVE-2023-31851.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-31853 ](CVE-2023/CVE-2023-318xx/CVE-2023-31853.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-34005 ](CVE-2023/CVE-2023-340xx/CVE-2023-34005.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-36511 ](CVE-2023/CVE-2023-365xx/CVE-2023-36511.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-36513 ](CVE-2023/CVE-2023-365xx/CVE-2023-36513.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-36514 ](CVE-2023/CVE-2023-365xx/CVE-2023-36514.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-37968 ](CVE-2023/CVE-2023-379xx/CVE-2023-37968.json ) (`2023-07-17T17:31:42.010` )
* [CVE-2023-1597 ](CVE-2023/CVE-2023-15xx/CVE-2023-1597.json ) (`2023-07-17T17:38:29.760` )
* [CVE-2023-32250 ](CVE-2023/CVE-2023-322xx/CVE-2023-32250.json ) (`2023-07-17T17:42:29.193` )
* [CVE-2023-35696 ](CVE-2023/CVE-2023-356xx/CVE-2023-35696.json ) (`2023-07-17T17:53:13.303` )
* [CVE-2023-32254 ](CVE-2023/CVE-2023-322xx/CVE-2023-32254.json ) (`2023-07-17T17:55:37.987` )
* [CVE-2023-1119 ](CVE-2023/CVE-2023-11xx/CVE-2023-1119.json ) (`2023-07-17T18:00:01.033` )
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.