Add CVE identifier to Vulnerability class

safety/safety.py

@@ -16,7 +16,7 @@
 
 
 class Vulnerability(namedtuple("Vulnerability",
-                               ["name", "spec", "version", "advisory", "vuln_id"])):
+                               ["name", "spec", "version", "advisory", "vuln_id", "cve"])):
     pass
 
 
@@ -156,7 +156,8 @@ def check(packages, key, db_mirror, cached, ignore_ids, proxy):
                                     spec=specifier,
                                     version=pkg.version,
                                     advisory=data.get("advisory"),
-                                    vuln_id=vuln_id
+                                    vuln_id=vuln_id,
+                                    cve=data.get("cve")
                                 )
                             )
     return vulnerable
@@ -171,6 +172,7 @@ def review(vulnerabilities):
             "version": vuln[2],
             "advisory": vuln[3],
             "vuln_id": vuln[4],
+            "cve": vuln[5],
         }
         vulnerable.append(
             Vulnerability(**current_vuln)

tests/test_db/example_report.json

@@ -4,20 +4,23 @@
         "<1.2.7",
         "1.2.2",
         "django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.",
-        "33063"
+        "33063",
+        "CVE-2011-4136"
     ],
     [
         "django",
         "<1.2.7",
         "1.2.2",
         "The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.",
-        "33064"
+        "33064",
+        "CVE-2011-4137"
     ],
     [
         "django",
         "<1.2.7",
         "1.2.2",
         "The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.",
-        "33065"
+        "33065",
+        "CVE-2011-4138"
     ]
 ]

tests/test_safety.py

@@ -84,6 +84,7 @@ def test_full_report(self):
                          + ' blah' * 15 + '.\r\n\r\n'
                          + 'All users are urged to upgrade please.\r\n',
                 vuln_id=1234,
+                cve="CVE-1234-5678"
             ),
         ]
         full_report = formatter.SheetReport.render(