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-09-19 16:00:28 +00:00
2023-09-19T16:00:24.964018+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-09-19 16:00:28 +00:00
2023-09-19T15:50:22.317000+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-09-19 02:00:27 +00:00
2023-09-19T00:00:13.565774+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-09-19 16:00:28 +00:00
225824
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-09-19 16:00:28 +00:00
Recently added CVEs: `11`
2023-09-15 23:55:28 +00:00
2023-09-19 16:00:28 +00:00
* [CVE-2022-47559 ](CVE-2022/CVE-2022-475xx/CVE-2022-47559.json ) (`2023-09-19T14:15:15.807` )
* [CVE-2023-31808 ](CVE-2023/CVE-2023-318xx/CVE-2023-31808.json ) (`2023-09-19T14:15:20.610` )
* [CVE-2023-41179 ](CVE-2023/CVE-2023-411xx/CVE-2023-41179.json ) (`2023-09-19T14:15:21.343` )
* [CVE-2023-4093 ](CVE-2023/CVE-2023-40xx/CVE-2023-4093.json ) (`2023-09-19T14:15:22.177` )
* [CVE-2023-4094 ](CVE-2023/CVE-2023-40xx/CVE-2023-4094.json ) (`2023-09-19T14:15:22.833` )
* [CVE-2023-4095 ](CVE-2023/CVE-2023-40xx/CVE-2023-4095.json ) (`2023-09-19T14:15:24.270` )
* [CVE-2023-4096 ](CVE-2023/CVE-2023-40xx/CVE-2023-4096.json ) (`2023-09-19T14:15:25.567` )
* [CVE-2023-3892 ](CVE-2023/CVE-2023-38xx/CVE-2023-3892.json ) (`2023-09-19T15:15:52.053` )
* [CVE-2023-41890 ](CVE-2023/CVE-2023-418xx/CVE-2023-41890.json ) (`2023-09-19T15:15:52.863` )
* [CVE-2023-42444 ](CVE-2023/CVE-2023-424xx/CVE-2023-42444.json ) (`2023-09-19T15:15:56.660` )
* [CVE-2023-42447 ](CVE-2023/CVE-2023-424xx/CVE-2023-42447.json ) (`2023-09-19T15:15:57.270` )
2023-08-31 06:00:30 +00:00
2023-09-01 12:00:28 +00:00
2023-09-06 02:00:29 +00:00
### CVEs modified in the last Commit
2023-09-05 22:00:27 +00:00
2023-09-19 16:00:28 +00:00
Recently modified CVEs: `17`
* [CVE-2021-28485 ](CVE-2021/CVE-2021-284xx/CVE-2021-28485.json ) (`2023-09-19T15:15:51.707` )
* [CVE-2023-4945 ](CVE-2023/CVE-2023-49xx/CVE-2023-4945.json ) (`2023-09-19T14:15:06.200` )
* [CVE-2023-20135 ](CVE-2023/CVE-2023-201xx/CVE-2023-20135.json ) (`2023-09-19T14:35:29.487` )
* [CVE-2023-4841 ](CVE-2023/CVE-2023-48xx/CVE-2023-4841.json ) (`2023-09-19T14:39:22.057` )
* [CVE-2023-4983 ](CVE-2023/CVE-2023-49xx/CVE-2023-4983.json ) (`2023-09-19T15:00:08.800` )
* [CVE-2023-4984 ](CVE-2023/CVE-2023-49xx/CVE-2023-4984.json ) (`2023-09-19T15:00:47.123` )
* [CVE-2023-5032 ](CVE-2023/CVE-2023-50xx/CVE-2023-5032.json ) (`2023-09-19T15:01:54.080` )
* [CVE-2023-4987 ](CVE-2023/CVE-2023-49xx/CVE-2023-4987.json ) (`2023-09-19T15:02:28.477` )
* [CVE-2023-41626 ](CVE-2023/CVE-2023-416xx/CVE-2023-41626.json ) (`2023-09-19T15:11:54.677` )
* [CVE-2023-40779 ](CVE-2023/CVE-2023-407xx/CVE-2023-40779.json ) (`2023-09-19T15:12:36.920` )
* [CVE-2023-37281 ](CVE-2023/CVE-2023-372xx/CVE-2023-37281.json ) (`2023-09-19T15:14:11.227` )
* [CVE-2023-37459 ](CVE-2023/CVE-2023-374xx/CVE-2023-37459.json ) (`2023-09-19T15:14:43.653` )
* [CVE-2023-4944 ](CVE-2023/CVE-2023-49xx/CVE-2023-4944.json ) (`2023-09-19T15:19:59.443` )
* [CVE-2023-40850 ](CVE-2023/CVE-2023-408xx/CVE-2023-40850.json ) (`2023-09-19T15:26:59.927` )
* [CVE-2023-3280 ](CVE-2023/CVE-2023-32xx/CVE-2023-3280.json ) (`2023-09-19T15:35:22.453` )
* [CVE-2023-20190 ](CVE-2023/CVE-2023-201xx/CVE-2023-20190.json ) (`2023-09-19T15:45:04.047` )
* [CVE-2023-20191 ](CVE-2023/CVE-2023-201xx/CVE-2023-20191.json ) (`2023-09-19T15:50:22.317` )
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.