2023-04-27 15:02:47 +02:00
# nvd-json-data-feeds
2023-04-24 14:55:30 +02:00
2024-03-26 17:03:58 +00:00
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/monitor_release.yml)
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/monitor_sync.yml)
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/validate_schema.yml)
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-27 19:03:28 +00:00
2024-03-27T19:00:37.713009+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-27 19:03:28 +00:00
2024-03-27T18:15:11.293000+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-27 03:03:27 +00:00
2024-03-27T01:00:20.271570+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-27 19:03:28 +00:00
243042
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-27 19:03:28 +00:00
Recently added CVEs: `27`
- [CVE-2024-20265 ](CVE-2024/CVE-2024-202xx/CVE-2024-20265.json ) (`2024-03-27T17:15:51.113` )
- [CVE-2024-20271 ](CVE-2024/CVE-2024-202xx/CVE-2024-20271.json ) (`2024-03-27T17:15:51.320` )
- [CVE-2024-20276 ](CVE-2024/CVE-2024-202xx/CVE-2024-20276.json ) (`2024-03-27T17:15:51.513` )
- [CVE-2024-20278 ](CVE-2024/CVE-2024-202xx/CVE-2024-20278.json ) (`2024-03-27T17:15:51.703` )
- [CVE-2024-20303 ](CVE-2024/CVE-2024-203xx/CVE-2024-20303.json ) (`2024-03-27T17:15:51.880` )
- [CVE-2024-20306 ](CVE-2024/CVE-2024-203xx/CVE-2024-20306.json ) (`2024-03-27T17:15:52.067` )
- [CVE-2024-20307 ](CVE-2024/CVE-2024-203xx/CVE-2024-20307.json ) (`2024-03-27T18:15:09.357` )
- [CVE-2024-20308 ](CVE-2024/CVE-2024-203xx/CVE-2024-20308.json ) (`2024-03-27T18:15:09.853` )
- [CVE-2024-20309 ](CVE-2024/CVE-2024-203xx/CVE-2024-20309.json ) (`2024-03-27T17:15:52.260` )
- [CVE-2024-20311 ](CVE-2024/CVE-2024-203xx/CVE-2024-20311.json ) (`2024-03-27T17:15:52.463` )
- [CVE-2024-20312 ](CVE-2024/CVE-2024-203xx/CVE-2024-20312.json ) (`2024-03-27T17:15:52.690` )
- [CVE-2024-20314 ](CVE-2024/CVE-2024-203xx/CVE-2024-20314.json ) (`2024-03-27T17:15:52.920` )
- [CVE-2024-20316 ](CVE-2024/CVE-2024-203xx/CVE-2024-20316.json ) (`2024-03-27T17:15:53.110` )
- [CVE-2024-20324 ](CVE-2024/CVE-2024-203xx/CVE-2024-20324.json ) (`2024-03-27T17:15:53.293` )
- [CVE-2024-20333 ](CVE-2024/CVE-2024-203xx/CVE-2024-20333.json ) (`2024-03-27T17:15:53.480` )
- [CVE-2024-20354 ](CVE-2024/CVE-2024-203xx/CVE-2024-20354.json ) (`2024-03-27T17:15:53.660` )
- [CVE-2024-23450 ](CVE-2024/CVE-2024-234xx/CVE-2024-23450.json ) (`2024-03-27T17:15:53.857` )
- [CVE-2024-23451 ](CVE-2024/CVE-2024-234xx/CVE-2024-23451.json ) (`2024-03-27T18:15:10.330` )
- [CVE-2024-2985 ](CVE-2024/CVE-2024-29xx/CVE-2024-2985.json ) (`2024-03-27T17:15:54.460` )
- [CVE-2024-2986 ](CVE-2024/CVE-2024-29xx/CVE-2024-2986.json ) (`2024-03-27T17:15:54.693` )
- [CVE-2024-2987 ](CVE-2024/CVE-2024-29xx/CVE-2024-2987.json ) (`2024-03-27T17:15:54.917` )
- [CVE-2024-2988 ](CVE-2024/CVE-2024-29xx/CVE-2024-2988.json ) (`2024-03-27T18:15:10.757` )
- [CVE-2024-2989 ](CVE-2024/CVE-2024-29xx/CVE-2024-2989.json ) (`2024-03-27T18:15:11.293` )
- [CVE-2024-29945 ](CVE-2024/CVE-2024-299xx/CVE-2024-29945.json ) (`2024-03-27T17:15:54.087` )
- [CVE-2024-29946 ](CVE-2024/CVE-2024-299xx/CVE-2024-29946.json ) (`2024-03-27T17:15:54.273` )
2024-03-07 00:55:36 +00:00
2024-03-21 19:04:35 +00:00
2024-03-22 03:03:20 +00:00
### CVEs modified in the last Commit
2024-03-21 23:03:27 +00:00
2024-03-27 19:03:28 +00:00
Recently modified CVEs: `6`
- [CVE-2023-5189 ](CVE-2023/CVE-2023-51xx/CVE-2023-5189.json ) (`2024-03-27T18:15:08.710` )
- [CVE-2024-1540 ](CVE-2024/CVE-2024-15xx/CVE-2024-1540.json ) (`2024-03-27T17:48:21.140` )
- [CVE-2024-1580 ](CVE-2024/CVE-2024-15xx/CVE-2024-1580.json ) (`2024-03-27T18:15:09.063` )
- [CVE-2024-2982 ](CVE-2024/CVE-2024-29xx/CVE-2024-2982.json ) (`2024-03-27T17:48:21.140` )
- [CVE-2024-2983 ](CVE-2024/CVE-2024-29xx/CVE-2024-2983.json ) (`2024-03-27T17:48:21.140` )
- [CVE-2024-2984 ](CVE-2024/CVE-2024-29xx/CVE-2024-2984.json ) (`2024-03-27T17:48:21.140` )
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-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.:
2024-03-26 17:03:58 +00:00
- Put the JSON feed into a document-based database and quickly leverage upon that data in your software project, ...
- 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-24 14:55:30 +02:00
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.