cedricbonhomme commited on
Commit
808245d
·
verified ·
1 Parent(s): a104085

Dataset card: CVSS v3/v4 fix, group split, fields

Browse files
Files changed (1) hide show
  1. README.md +65 -3
README.md CHANGED
@@ -60,13 +60,75 @@ dataset_info:
60
 
61
  # Vulnerability-FSTEC
62
 
63
- Vulnerability descriptions and severity labels from the [FSTEC](https://vulnerability.circl.lu/recent#fstec), extracted via [Vulnerability-Lookup](https://vulnerability.circl.lu).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
64
 
65
  ## Source
66
 
67
- - **Data source**: [Vulnerability-Lookup](https://vulnerability.circl.lu) API
68
- - **Extraction tool**: [VulnTrain](https://github.com/vulnerability-lookup/VulnTrain)
69
 
70
  ## Related models
71
 
72
  - [CIRCL/vulnerability-severity-classification-russian-ruRoberta-large](https://huggingface.co/CIRCL/vulnerability-severity-classification-russian-ruRoberta-large) — severity classifier trained on this dataset
 
 
 
 
 
 
 
 
 
60
 
61
  # Vulnerability-FSTEC
62
 
63
+ Russian vulnerability descriptions with CVSS scores from the Data Bank of Security Threats (BDU) of [FSTEC of Russia](https://bdu.fstec.ru), extracted via [Vulnerability-Lookup](https://vulnerability.circl.lu/recent#fstec).
64
+ It is used to train the VLAI severity classifier for Russian.
65
+
66
+ > **Revision a104085 (2026-11-03) fixes the CVSS scores.** Earlier revisions had CVSS 2.0 scores only: BDU stores its v3 and v4 vectors without the `CVSS:3.x/` / `CVSS:4.0/` prefix, and the parser dropped them silently.
67
+ > Reading them changes the severity label of 21,457 of the 82,960 rows of the previous revision (25.9%).
68
+ > This revision also has a group-aware train/validation/test split. Reported and fixed by Christian Bucher, see [VulnTrain #28](https://github.com/vulnerability-lookup/VulnTrain/pull/28).
69
+
70
+ ## Splits
71
+
72
+ | Split | Rows | Low | Medium | High | Critical |
73
+ |---|---:|---:|---:|---:|---:|
74
+ | train | 78,798 | 2,513 | 31,196 | 32,758 | 12,329 |
75
+ | validation | 10,027 | 288 | 4,209 | 4,154 | 1,376 |
76
+ | test | 9,698 | 290 | 3,928 | 4,033 | 1,447 |
77
+ | **total** | **98,523** | 3,091 (3.1%) | 39,333 (39.9%) | 40,945 (41.6%) | 15,152 (15.4%) |
78
+
79
+ Two train rows have no usable score and no label.
80
+
81
+ Rows that share a normalised description or a CVE id are kept in the same split, and each group's split comes from a seeded hash, so a record stays in its split when the dataset is rebuilt.
82
+ The published revision has no description or CVE id shared between splits (checked with [`check_split_leakage.py`](https://github.com/vulnerability-lookup/VulnTrain/tree/main/tools/dataset)).
83
+
84
+ ## Fields
85
+
86
+ | Field | Description |
87
+ |---|---|
88
+ | `id` | BDU identifier, e.g. `BDU:2021-05687` |
89
+ | `title` | Vulnerability name (Russian) |
90
+ | `description` | Vulnerability description (Russian) |
91
+ | `cvss_v4_0` | CVSS 4.0 base score, base metrics only (CVSS-B), as for the other VLAI datasets (5,037 rows) |
92
+ | `cvss_v3_0` | CVSS 3.x base score (81,177 rows) |
93
+ | `cvss_v2_0` | CVSS 2.0 base score (98,519 rows) |
94
+ | `cvss_v3_1` | Always empty: BDU gives one v3 vector, stored in `cvss_v3_0` |
95
+ | `cve_id` | First CVE id among the record's identifiers in other databases (95,504 rows, 96.9%) |
96
+ | `other_identifiers` | That field as published by BDU, e.g. `CVE-2009-3585, DSA-1944, ID:1400490` |
97
+ | `source` | Always `fstec` |
98
+ | `cpes`, `aliases` | Always empty; kept for a schema shared with the other VLAI datasets |
99
+
100
+ ## Severity labels
101
+
102
+ The dataset stores scores, not labels. The VLAI trainers take the first available score in the order v4.0, v3.x, v2.0 and map it to Low (< 4.0), Medium (4.0–6.9), High (7.0–8.9) or Critical (≥ 9.0).
103
+ In this revision, 77.3% of the labels come from v3, 17.6% from v2 and 5.1% from v4.
104
+
105
+ How the vectors are read:
106
+ - BDU's v3 and v4 vectors have no `CVSS:3.x/` / `CVSS:4.0/` prefix; it is added before scoring.
107
+ - v4.0 is scored on its base metrics only (CVSS-B). Threat metrics such as Exploit Maturity are left out.
108
+ - A vector with no impact at all (`C:N/I:N/A:N`, score 0.0) is a placeholder in BDU and is treated as missing.
109
+
110
+ ## Usage
111
+
112
+ ```python
113
+ from datasets import load_dataset
114
+
115
+ dataset = load_dataset("CIRCL/Vulnerability-FSTEC", revision="a104085")
116
+ print(dataset)
117
+ ```
118
 
119
  ## Source
120
 
121
+ - **Data source**: BDU of FSTEC of Russia, via [Vulnerability-Lookup](https://vulnerability.circl.lu)
122
+ - **Extraction tool**: [VulnTrain](https://github.com/vulnerability-lookup/VulnTrain) (`vulntrain-dataset-generation --sources fstec --validation-size 0.1`)
123
 
124
  ## Related models
125
 
126
  - [CIRCL/vulnerability-severity-classification-russian-ruRoberta-large](https://huggingface.co/CIRCL/vulnerability-severity-classification-russian-ruRoberta-large) — severity classifier trained on this dataset
127
+
128
+ ## Acknowledgements
129
+
130
+ Thanks to Christian Bucher ([christian140903-sudo](https://github.com/christian140903-sudo)) for finding and fixing the CVSS reading and the `cve_id` field.
131
+
132
+ ## Funding
133
+
134
+ This work is part of [AIPITCH](https://www.science.nask.pl/en/research-areas/projects/12456).