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-19 18:01:01 +00:00
2023-07-19T18:00:58.031131+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-19 18:01:01 +00:00
2023-07-19T17:56:49.593000+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-19 02:01:21 +00:00
2023-07-19T00:00:13.554713+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-19 18:01:01 +00:00
220689
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-19 18:01:01 +00:00
Recently added CVEs: `6`
2023-07-18 23:55:42 +00:00
2023-07-19 18:01:01 +00:00
* [CVE-2023-25838 ](CVE-2023/CVE-2023-258xx/CVE-2023-25838.json ) (`2023-07-19T16:15:09.540` )
* [CVE-2023-25839 ](CVE-2023/CVE-2023-258xx/CVE-2023-25839.json ) (`2023-07-19T16:15:09.640` )
* [CVE-2023-32261 ](CVE-2023/CVE-2023-322xx/CVE-2023-32261.json ) (`2023-07-19T16:15:09.737` )
* [CVE-2023-32262 ](CVE-2023/CVE-2023-322xx/CVE-2023-32262.json ) (`2023-07-19T16:15:09.817` )
* [CVE-2023-32263 ](CVE-2023/CVE-2023-322xx/CVE-2023-32263.json ) (`2023-07-19T16:15:09.893` )
* [CVE-2023-37748 ](CVE-2023/CVE-2023-377xx/CVE-2023-37748.json ) (`2023-07-19T17:15:22.323` )
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-19 18:01:01 +00:00
Recently modified CVEs: `63`
* [CVE-2023-30922 ](CVE-2023/CVE-2023-309xx/CVE-2023-30922.json ) (`2023-07-19T17:10:01.970` )
* [CVE-2023-30924 ](CVE-2023/CVE-2023-309xx/CVE-2023-30924.json ) (`2023-07-19T17:10:04.407` )
* [CVE-2023-30925 ](CVE-2023/CVE-2023-309xx/CVE-2023-30925.json ) (`2023-07-19T17:10:07.203` )
* [CVE-2023-30927 ](CVE-2023/CVE-2023-309xx/CVE-2023-30927.json ) (`2023-07-19T17:10:12.373` )
* [CVE-2023-30926 ](CVE-2023/CVE-2023-309xx/CVE-2023-30926.json ) (`2023-07-19T17:12:46.443` )
* [CVE-2023-35874 ](CVE-2023/CVE-2023-358xx/CVE-2023-35874.json ) (`2023-07-19T17:13:20.070` )
* [CVE-2023-3023 ](CVE-2023/CVE-2023-30xx/CVE-2023-3023.json ) (`2023-07-19T17:13:40.433` )
* [CVE-2023-22506 ](CVE-2023/CVE-2023-225xx/CVE-2023-22506.json ) (`2023-07-19T17:15:22.070` )
* [CVE-2023-33253 ](CVE-2023/CVE-2023-332xx/CVE-2023-33253.json ) (`2023-07-19T17:15:22.167` )
* [CVE-2023-33876 ](CVE-2023/CVE-2023-338xx/CVE-2023-33876.json ) (`2023-07-19T17:15:22.243` )
* [CVE-2023-3131 ](CVE-2023/CVE-2023-31xx/CVE-2023-3131.json ) (`2023-07-19T17:15:43.263` )
* [CVE-2023-3209 ](CVE-2023/CVE-2023-32xx/CVE-2023-3209.json ) (`2023-07-19T17:16:05.520` )
* [CVE-2023-3271 ](CVE-2023/CVE-2023-32xx/CVE-2023-3271.json ) (`2023-07-19T17:16:17.150` )
* [CVE-2023-3202 ](CVE-2023/CVE-2023-32xx/CVE-2023-3202.json ) (`2023-07-19T17:21:53.547` )
* [CVE-2023-33170 ](CVE-2023/CVE-2023-331xx/CVE-2023-33170.json ) (`2023-07-19T17:25:39.773` )
* [CVE-2023-33173 ](CVE-2023/CVE-2023-331xx/CVE-2023-33173.json ) (`2023-07-19T17:27:22.683` )
* [CVE-2023-33174 ](CVE-2023/CVE-2023-331xx/CVE-2023-33174.json ) (`2023-07-19T17:28:11.077` )
* [CVE-2023-3166 ](CVE-2023/CVE-2023-31xx/CVE-2023-3166.json ) (`2023-07-19T17:39:27.673` )
* [CVE-2023-25194 ](CVE-2023/CVE-2023-251xx/CVE-2023-25194.json ) (`2023-07-19T17:42:24.030` )
* [CVE-2023-3158 ](CVE-2023/CVE-2023-31xx/CVE-2023-3158.json ) (`2023-07-19T17:43:47.977` )
* [CVE-2023-3167 ](CVE-2023/CVE-2023-31xx/CVE-2023-3167.json ) (`2023-07-19T17:46:13.803` )
* [CVE-2023-37198 ](CVE-2023/CVE-2023-371xx/CVE-2023-37198.json ) (`2023-07-19T17:52:50.213` )
* [CVE-2023-29298 ](CVE-2023/CVE-2023-292xx/CVE-2023-29298.json ) (`2023-07-19T17:55:22.400` )
* [CVE-2023-37197 ](CVE-2023/CVE-2023-371xx/CVE-2023-37197.json ) (`2023-07-19T17:55:59.233` )
* [CVE-2023-37196 ](CVE-2023/CVE-2023-371xx/CVE-2023-37196.json ) (`2023-07-19T17:56:49.593` )
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.