2023-04-27 15:02:47 +02:00
# nvd-json-data-feeds
2023-04-24 14:55:30 +02:00
2023-12-15 13:00:27 +00:00
Community reconstruction of the 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
2024-03-07 12:27:24 +00:00
2024-03-07T12:24:07.874550+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
2024-03-07 11:02:23 +00:00
2024-03-07T10:15:07.260000+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
2024-03-07 03:00:28 +00:00
2024-03-07T01:00:28.284195+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
2024-03-07 11:02:23 +00:00
240767
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
2024-03-07 12:27:24 +00:00
Recently added CVEs: `4`
2024-02-29 17:00:29 +00:00
2024-03-07 12:27:24 +00:00
* [CVE-2022-36769 ](CVE-2022/CVE-2022-367xx/CVE-2022-36769.json ) (`2023-04-26T03:15:08.663` )
* [CVE-2023-30839 ](CVE-2023/CVE-2023-308xx/CVE-2023-30839.json ) (`2023-04-25T19:15:11.247` )
* [CVE-2024-0069 ](CVE-2024/CVE-2024-00xx/CVE-2024-0069.json ) (`2023-11-28T00:15:07.140` )
* [CVE-2024-0070 ](CVE-2024/CVE-2024-00xx/CVE-2024-0070.json ) (`2023-11-28T00:15:07.183` )
2024-03-04 19:00:36 +00:00
2024-03-06 19:00:36 +00:00
2024-03-07 12:27:24 +00:00
### CVEs modified in the last Commit
2024-03-07 00:55:36 +00:00
2024-03-07 12:27:24 +00:00
Recently modified CVEs: `450`
* [CVE-2023-43791 ](CVE-2023/CVE-2023-437xx/CVE-2023-43791.json ) (`2023-11-18T00:55:15.610` )
* [CVE-2023-43804 ](CVE-2023/CVE-2023-438xx/CVE-2023-43804.json ) (`2024-02-01T00:55:23.317` )
* [CVE-2023-44361 ](CVE-2023/CVE-2023-443xx/CVE-2023-44361.json ) (`2023-11-22T17:03:38.187` )
* [CVE-2023-46230 ](CVE-2023/CVE-2023-462xx/CVE-2023-46230.json ) (`2024-02-05T21:00:21.200` )
* [CVE-2023-46886 ](CVE-2023/CVE-2023-468xx/CVE-2023-46886.json ) (`2023-12-05T13:02:07.903` )
* [CVE-2023-47640 ](CVE-2023/CVE-2023-476xx/CVE-2023-47640.json ) (`2023-11-22T15:00:49.287` )
* [CVE-2023-50578 ](CVE-2023/CVE-2023-505xx/CVE-2023-50578.json ) (`2024-01-08T15:00:22.667` )
* [CVE-2023-51842 ](CVE-2023/CVE-2023-518xx/CVE-2023-51842.json ) (`2024-02-06T17:00:29.330` )
* [CVE-2023-52269 ](CVE-2023/CVE-2023-522xx/CVE-2023-52269.json ) (`2024-01-05T23:00:11.447` )
* [CVE-2023-5369 ](CVE-2023/CVE-2023-53xx/CVE-2023-5369.json ) (`2023-11-24T09:15:09.607` )
* [CVE-2023-5370 ](CVE-2023/CVE-2023-53xx/CVE-2023-5370.json ) (`2023-11-24T09:15:09.677` )
* [CVE-2023-5568 ](CVE-2023/CVE-2023-55xx/CVE-2023-5568.json ) (`2023-11-24T09:15:09.767` )
* [CVE-2023-6378 ](CVE-2023/CVE-2023-63xx/CVE-2023-6378.json ) (`2023-12-05T21:00:10.557` )
* [CVE-2023-6546 ](CVE-2023/CVE-2023-65xx/CVE-2023-6546.json ) (`2024-02-28T15:15:07.593` )
* [CVE-2023-6959 ](CVE-2023/CVE-2023-69xx/CVE-2023-6959.json ) (`2024-02-14T17:01:57.227` )
* [CVE-2023-6963 ](CVE-2023/CVE-2023-69xx/CVE-2023-6963.json ) (`2024-02-14T17:05:16.533` )
* [CVE-2024-0193 ](CVE-2024/CVE-2024-01xx/CVE-2024-0193.json ) (`2024-02-28T15:15:08.547` )
* [CVE-2024-0705 ](CVE-2024/CVE-2024-07xx/CVE-2024-0705.json ) (`2024-01-26T19:00:15.863` )
* [CVE-2024-21599 ](CVE-2024/CVE-2024-215xx/CVE-2024-21599.json ) (`2024-01-19T21:00:23.387` )
* [CVE-2024-24772 ](CVE-2024/CVE-2024-247xx/CVE-2024-24772.json ) (`2024-02-28T15:15:09.093` )
* [CVE-2024-24773 ](CVE-2024/CVE-2024-247xx/CVE-2024-24773.json ) (`2024-02-28T15:15:09.177` )
* [CVE-2024-24779 ](CVE-2024/CVE-2024-247xx/CVE-2024-24779.json ) (`2024-02-28T15:15:09.250` )
* [CVE-2024-26016 ](CVE-2024/CVE-2024-260xx/CVE-2024-26016.json ) (`2024-02-28T15:15:09.320` )
* [CVE-2024-26464 ](CVE-2024/CVE-2024-264xx/CVE-2024-26464.json ) (`2024-02-28T15:15:09.390` )
* [CVE-2024-27315 ](CVE-2024/CVE-2024-273xx/CVE-2024-27315.json ) (`2024-02-28T15:15:09.670` )
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-12-21 15:00:28 +00:00
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-12-21 15:00:28 +00:00
#### (Optional) Meta Files
Similar to the old official feeds, we provide meta files with each release. They can be fetched for each feed via:
```sh
https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-< YEAR > .meta
```
The structure is as follows:
```plain
lastModifiedDate:1970-01-01T00:00:00.000+00:00 # ISO 8601 timestamp of last CVE modification
size:1000 # size of uncompressed feed (bytes)
xzSize:100 # size of lzma-compressed feed (bytes)
sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 # sha256 hexdigest of uncompressed feed
```
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-12-15 13:00:27 +00:00
On 2023-12-15, the NIST deprecated 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.