- CVE entries in our dataset cover the period from 2002 to 2019, each consisting of 21 features. Each feature's name and corresponding column name in the CSV file are explained in the following table. The dataset is released as comma-separated values(CSV) format (all_c_cpp_release2.0.csv).
| Features | Column Name in the CSV | Description |
|---|---|---|
| Access Complexity | access_complexity | Reflects the complexity of the attack required to exploit the software feature misuse vulnerability |
| Authentication Required | authentication_required | If authentication is required to exploit the vulnerability |
| Availability Impact | availability_impact | Measures the potential impact to availability of a successfully exploited misuse vulnerability |
| Commit ID | commit_id | Commit ID in code repository, indicating a mini-version |
| Commit Message | commit_message | Commit message from developer |
| Confidentiality Impact | confidentiality_impact | Measures the potential impact on confidentiality of a successfully exploited misuse vulnerability |
| CWE ID | cwe_id | Common Weakness Enumeration ID |
| CVE ID | cve_id | Common Vulnerabilities and Exposures ID |
| CVE Page | cve_page | CVE Details web page link for that CVE |
| CVE Summary | summary | CVE summary information |
| CVSS Score | score | The relative severity of software flaw vulnerabilities |
| Files Changed | files_changed | All the changed files and corresponding patches |
| Integrity Impact | integrity_impact | Measures the potential impact to integrity of a successfully exploited misuse vulnerability\ |
| Mini-version After Fix | version_after_fix | Mini-version ID after the fix |
| Mini-version Before Fix | version_before_fix | Mini-version ID before the fix |
| Programming Language | lang | Project programming language |
| Project | project | Project name |
| Publish Date | publish_date | Publish date of the CVE |
| Reference Link | ref_ink | Reference link in the CVE page |
| Update Date | update_date | Update date of the CVE |
| Vulnerability Classification | vulnerability_classification | Vulnerability type |
-
We used the code changes information(minned from commited version patches) to localize which lines of code in the files were modified. Taking modified lines between the two mini-versions as flaw lines, we split the functions in the modified files into vulnerable functions (if there were flaw lines modified in the function) and non-vulnerable functions.
-
The cleaned version of split functions is coming soon.
-
Pre-Requirements
-
How to use
- First use scrape_all_the_cve.py to scrape all the CVE entries on CVE Details
- Then use get_commit_info to get commit messages
- Finally crawl down all the source files and patch files using commit messages above, and then split all the functions in the modified files, see all_cpp_c_project_with_chrome_android.ipynb for details.
ACM Reference Format:
Jiahao Fan, Yi Li, Shaohua Wang and Tien N. Nguyen. 2020. A C/C++ Code Vulnerability Dataset with Code Changes and CVE Summaries. In MSR ’20: The 17th International Conference on Mining Software Repositories,May 25–26, 2020, MSR, Seoul, South Korea. ACM, New York, NY, USA, 5 pages. https://doi.org/10.1145/3379597.3387501
-
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent