cedricbonhomme commited on
Commit
15469a5
·
verified ·
1 Parent(s): f7a1cd2

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +19 -7
README.md CHANGED
@@ -7,6 +7,8 @@ tags:
7
  model-index:
8
  - name: vulnerability-description-generation-gpt2-large
9
  results: []
 
 
10
  ---
11
 
12
  <!-- This model card has been generated automatically according to the information the Trainer had access to. You
@@ -14,21 +16,31 @@ should probably proofread and complete it, then remove this comment. -->
14
 
15
  # vulnerability-description-generation-gpt2-large
16
 
17
- This model is a fine-tuned version of [openai-community/gpt2-large](https://huggingface.co/openai-community/gpt2-large) on an unknown dataset.
 
18
  It achieves the following results on the evaluation set:
19
  - Loss: 1.2889
20
 
 
 
 
 
 
 
21
  ## Model description
22
 
23
- More information needed
24
 
25
- ## Intended uses & limitations
26
 
27
- More information needed
28
 
29
- ## Training and evaluation data
 
 
30
 
31
- More information needed
 
 
32
 
33
  ## Training procedure
34
 
@@ -58,4 +70,4 @@ The following hyperparameters were used during training:
58
  - Transformers 4.49.0
59
  - Pytorch 2.6.0+cu124
60
  - Datasets 3.4.0
61
- - Tokenizers 0.21.1
 
7
  model-index:
8
  - name: vulnerability-description-generation-gpt2-large
9
  results: []
10
+ datasets:
11
+ - CIRCL/vulnerability
12
  ---
13
 
14
  <!-- This model card has been generated automatically according to the information the Trainer had access to. You
 
16
 
17
  # vulnerability-description-generation-gpt2-large
18
 
19
+ This model is a fine-tuned version of [openai-community/gpt2-large](https://huggingface.co/openai-community/gpt2-large) on the dataset [CIRCL/vulnerability](https://huggingface.co/datasets/CIRCL/vulnerability).
20
+
21
  It achieves the following results on the evaluation set:
22
  - Loss: 1.2889
23
 
24
+ codecarbon information:
25
+ - Energy consumed for RAM : 2.726718 kWh. RAM Power : 94.34470081329346 W
26
+ - Energy consumed for all CPUs : 1.228363 kWh. Total CPU Power : 42.5 W
27
+ - Energy consumed for all GPUs : 14.324482 kWh. Total GPU Power : 171.6372824939248 W
28
+ - 18.279562 kWh of electricity used since the beginning.
29
+
30
  ## Model description
31
 
32
+ It is a text generation model and is aimed to assist in writing vulnerability descriptions.
33
 
 
34
 
35
+ ## How to get started with the model
36
 
37
+ ```python
38
+ from transformers import pipeline
39
+ pipe = pipeline("text-generation", model="CIRCL/vulnerability-description-generation-gpt2-large")
40
 
41
+ >>> print(pipe("A new vulnerability in OpenSSL allows", max_length=300))
42
+ [{'generated_text': 'A new vulnerability in OpenSSL allows remote attackers to create insecure connections. The impact of this vulnerability is that one or more TLS connections will be created under one username or one username/logon in a session for which another username or logon is valid. An attacker that can control the username or logon string of an openSSL host can effectively manipulate the OpenSSL host in a way that enables the attacker to create arbitrary openSSL connections by calling `http-server-create` in a non-secure sequence across other hosts. The vulnerability may be used to perform a man-in-the-middle attack, making the attacker completely different to the attacker. An exploitation may include MITM attacks and man-in-the-middle attacks. NOTE: the vendor states that "SUSE OpenSSL\'s implementation of \'openSSL_connect`, is not vulnerable to MITM attacks. If the attack vector is a MITM attack, OpenSSL will work under any circumstances." The CVE has been assigned for tracking purposes. In no way does the vendor\'s position change that an OpenSSL client should not use openSSL in the context of another OpenSSL server, but an attacker must choose the vulnerability according to their configuration if they are to exploit their attack. NOTE: the vendor indicates that it has considered the impact of this vulnerability "moderate". If by any measure, an OpenSSL client is susceptible to MITM attacks, that vulnerability would be considered low because it would be difficult to exploit a vulnerability that'}]
43
+ ```
44
 
45
  ## Training procedure
46
 
 
70
  - Transformers 4.49.0
71
  - Pytorch 2.6.0+cu124
72
  - Datasets 3.4.0
73
+ - Tokenizers 0.21.1