Modify the container name

koumoul-dev · Jul 31, 2023 · c517fea · c517fea
1 parent be0af05
commit c517fea
Show file tree

Hide file tree

Showing 3 changed files with 74 additions and 8 deletions.
diff --git a/app.js b/app.js
@@ -26,6 +26,7 @@ const runAllScans = async () => {
       if (scanTarget.type === 'image') {
         const imageRef = parseQualifiedName(scanTarget.name)
         for (const container of containers.filter(container => container.image === scanTarget.name)) {
+          container.name[0] = container.name[0].replace('/', '')
           gaugeImageVulnerabilities.set({
             container_name: container.name,
             severity: counter.severity,
@@ -53,6 +54,7 @@ const runAllScans = async () => {
         console.log('Vulnerabilities', vulnerabilities)
         for (const vulnerability of vulnerabilities) {
           for (const container of containers.filter(container => container.image === scanTarget.name)) {
+            container.name[0] = container.name[0].replace('/', '')
             gaugeVulnerabilityID.set({
               container_name: container.name,
               severity: vulnerability.Severity,

diff --git a/data/alpine:3.17.0-scan-report.json b/data/alpine:3.17.0-scan-report.json
@@ -1119,6 +1119,7 @@
           "Layer": {
             "DiffID": "sha256:ded7a220bb058e28ee3254fbba04ca90b679070424424761a53a043b93b612bf"
           },
+          "SeveritySource": "nvd",
           "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2023-2975",
           "DataSource": {
             "ID": "alpine",
@@ -1128,7 +1129,14 @@
           "Title": "AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries",
           "Description": "Issue summary: The AES-SIV cipher implementation contains a bug that causes\nit to ignore empty associated data entries which are unauthenticated as\na consequence.\n\nImpact summary: Applications that use the AES-SIV algorithm and want to\nauthenticate empty data entries as associated data can be mislead by removing\nadding or reordering such empty entries as these are ignored by the OpenSSL\nimplementation. We are currently unaware of any such applications.\n\nThe AES-SIV algorithm allows for authentication of multiple associated\ndata entries along with the encryption. To authenticate empty data the\napplication has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with\nNULL pointer as the output buffer and 0 as the input buffer length.\nThe AES-SIV implementation in OpenSSL just returns success for such a call\ninstead of performing the associated data authentication operation.\nThe empty data thus will not be authenticated.\n\nAs this issue does not affect non-empty associated data authentication and\nwe expect it to be rare for an application to use empty associated data\nentries this is qualified as Low severity issue.",
           "Severity": "MEDIUM",
+          "CweIDs": [
+            "CWE-287"
+          ],
           "CVSS": {
+            "nvd": {
+              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
+              "V3Score": 5.3
+            },
             "redhat": {
               "V3Vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
               "V3Score": 5.9
@@ -1147,7 +1155,7 @@
             "https://www.openssl.org/news/secadv/20230714.txt"
           ],
           "PublishedDate": "2023-07-14T12:15:00Z",
-          "LastModifiedDate": "2023-07-25T15:15:00Z"
+          "LastModifiedDate": "2023-07-27T13:02:00Z"
         },
         {
           "VulnerabilityID": "CVE-2023-3446",
@@ -1158,6 +1166,7 @@
           "Layer": {
             "DiffID": "sha256:ded7a220bb058e28ee3254fbba04ca90b679070424424761a53a043b93b612bf"
           },
+          "SeveritySource": "nvd",
           "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2023-3446",
           "DataSource": {
             "ID": "alpine",
@@ -1167,7 +1176,14 @@
           "Title": "Excessive time spent checking DH keys and parameters",
           "Description": "Issue summary: Checking excessively long DH keys or parameters may be very slow.\n\nImpact summary: Applications that use the functions DH_check(), DH_check_ex()\nor EVP_PKEY_param_check() to check a DH key or DH parameters may experience long\ndelays. Where the key or parameters that are being checked have been obtained\nfrom an untrusted source this may lead to a Denial of Service.\n\nThe function DH_check() performs various checks on DH parameters. One of those\nchecks confirms that the modulus ('p' parameter) is not too large. Trying to use\na very large modulus is slow and OpenSSL will not normally use a modulus which\nis over 10,000 bits in length.\n\nHowever the DH_check() function checks numerous aspects of the key or parameters\nthat have been supplied. Some of those checks use the supplied modulus value\neven if it has already been found to be too large.\n\nAn application that calls DH_check() and supplies a key or parameters obtained\nfrom an untrusted source could be vulernable to a Denial of Service attack.\n\nThe function DH_check() is itself called by a number of other OpenSSL functions.\nAn application calling any of those other functions may similarly be affected.\nThe other functions affected by this are DH_check_ex() and\nEVP_PKEY_param_check().\n\nAlso vulnerable are the OpenSSL dhparam and pkeyparam command line applications\nwhen using the '-check' option.\n\nThe OpenSSL SSL/TLS implementation is not affected by this issue.\nThe OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.",
           "Severity": "MEDIUM",
+          "CweIDs": [
+            "CWE-1333"
+          ],
           "CVSS": {
+            "nvd": {
+              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
+              "V3Score": 5.3
+            },
             "redhat": {
               "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
               "V3Score": 5.3
@@ -1188,7 +1204,7 @@
             "https://www.openssl.org/news/secadv/20230719.txt"
           ],
           "PublishedDate": "2023-07-19T12:15:00Z",
-          "LastModifiedDate": "2023-07-19T18:15:00Z"
+          "LastModifiedDate": "2023-07-28T19:02:00Z"
         },
         {
           "VulnerabilityID": "CVE-2022-3996",
@@ -2252,6 +2268,7 @@
           "Layer": {
             "DiffID": "sha256:ded7a220bb058e28ee3254fbba04ca90b679070424424761a53a043b93b612bf"
           },
+          "SeveritySource": "nvd",
           "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2023-2975",
           "DataSource": {
             "ID": "alpine",
@@ -2261,7 +2278,14 @@
           "Title": "AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries",
           "Description": "Issue summary: The AES-SIV cipher implementation contains a bug that causes\nit to ignore empty associated data entries which are unauthenticated as\na consequence.\n\nImpact summary: Applications that use the AES-SIV algorithm and want to\nauthenticate empty data entries as associated data can be mislead by removing\nadding or reordering such empty entries as these are ignored by the OpenSSL\nimplementation. We are currently unaware of any such applications.\n\nThe AES-SIV algorithm allows for authentication of multiple associated\ndata entries along with the encryption. To authenticate empty data the\napplication has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with\nNULL pointer as the output buffer and 0 as the input buffer length.\nThe AES-SIV implementation in OpenSSL just returns success for such a call\ninstead of performing the associated data authentication operation.\nThe empty data thus will not be authenticated.\n\nAs this issue does not affect non-empty associated data authentication and\nwe expect it to be rare for an application to use empty associated data\nentries this is qualified as Low severity issue.",
           "Severity": "MEDIUM",
+          "CweIDs": [
+            "CWE-287"
+          ],
           "CVSS": {
+            "nvd": {
+              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
+              "V3Score": 5.3
+            },
             "redhat": {
               "V3Vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
               "V3Score": 5.9
@@ -2280,7 +2304,7 @@
             "https://www.openssl.org/news/secadv/20230714.txt"
           ],
           "PublishedDate": "2023-07-14T12:15:00Z",
-          "LastModifiedDate": "2023-07-25T15:15:00Z"
+          "LastModifiedDate": "2023-07-27T13:02:00Z"
         },
         {
           "VulnerabilityID": "CVE-2023-3446",
@@ -2291,6 +2315,7 @@
           "Layer": {
             "DiffID": "sha256:ded7a220bb058e28ee3254fbba04ca90b679070424424761a53a043b93b612bf"
           },
+          "SeveritySource": "nvd",
           "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2023-3446",
           "DataSource": {
             "ID": "alpine",
@@ -2300,7 +2325,14 @@
           "Title": "Excessive time spent checking DH keys and parameters",
           "Description": "Issue summary: Checking excessively long DH keys or parameters may be very slow.\n\nImpact summary: Applications that use the functions DH_check(), DH_check_ex()\nor EVP_PKEY_param_check() to check a DH key or DH parameters may experience long\ndelays. Where the key or parameters that are being checked have been obtained\nfrom an untrusted source this may lead to a Denial of Service.\n\nThe function DH_check() performs various checks on DH parameters. One of those\nchecks confirms that the modulus ('p' parameter) is not too large. Trying to use\na very large modulus is slow and OpenSSL will not normally use a modulus which\nis over 10,000 bits in length.\n\nHowever the DH_check() function checks numerous aspects of the key or parameters\nthat have been supplied. Some of those checks use the supplied modulus value\neven if it has already been found to be too large.\n\nAn application that calls DH_check() and supplies a key or parameters obtained\nfrom an untrusted source could be vulernable to a Denial of Service attack.\n\nThe function DH_check() is itself called by a number of other OpenSSL functions.\nAn application calling any of those other functions may similarly be affected.\nThe other functions affected by this are DH_check_ex() and\nEVP_PKEY_param_check().\n\nAlso vulnerable are the OpenSSL dhparam and pkeyparam command line applications\nwhen using the '-check' option.\n\nThe OpenSSL SSL/TLS implementation is not affected by this issue.\nThe OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.",
           "Severity": "MEDIUM",
+          "CweIDs": [
+            "CWE-1333"
+          ],
           "CVSS": {
+            "nvd": {
+              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
+              "V3Score": 5.3
+            },
             "redhat": {
               "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
               "V3Score": 5.3
@@ -2321,7 +2353,7 @@
             "https://www.openssl.org/news/secadv/20230719.txt"
           ],
           "PublishedDate": "2023-07-19T12:15:00Z",
-          "LastModifiedDate": "2023-07-19T18:15:00Z"
+          "LastModifiedDate": "2023-07-28T19:02:00Z"
         }
       ]
     }