diff --git a/2017/17xxx/CVE-2017-17305.json b/2017/17xxx/CVE-2017-17305.json
index e0731f655b0..74dabf56d47 100644
--- a/2017/17xxx/CVE-2017-17305.json
+++ b/2017/17xxx/CVE-2017-17305.json
@@ -62,6 +62,8 @@
    "references" : {
       "reference_data" : [
          {
+            "name" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en",
+            "refsource" : "CONFIRM",
             "url" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en"
          }
       ]
diff --git a/2017/17xxx/CVE-2017-17311.json b/2017/17xxx/CVE-2017-17311.json
index 94e94fdedb7..ea1f0550f3f 100644
--- a/2017/17xxx/CVE-2017-17311.json
+++ b/2017/17xxx/CVE-2017-17311.json
@@ -62,6 +62,8 @@
    "references" : {
       "reference_data" : [
          {
+            "name" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en",
+            "refsource" : "CONFIRM",
             "url" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en"
          }
       ]
diff --git a/2017/17xxx/CVE-2017-17312.json b/2017/17xxx/CVE-2017-17312.json
index 9ad8988d88f..cd349517c04 100644
--- a/2017/17xxx/CVE-2017-17312.json
+++ b/2017/17xxx/CVE-2017-17312.json
@@ -62,6 +62,8 @@
    "references" : {
       "reference_data" : [
          {
+            "name" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en",
+            "refsource" : "CONFIRM",
             "url" : "https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180813-01-Bleichenbacher-en"
          }
       ]
diff --git a/2018/12xxx/CVE-2018-12115.json b/2018/12xxx/CVE-2018-12115.json
index f8c6e88b375..118517bec7d 100644
--- a/2018/12xxx/CVE-2018-12115.json
+++ b/2018/12xxx/CVE-2018-12115.json
@@ -35,7 +35,7 @@
       "description_data" : [
          {
             "lang" : "eng",
-            "value" : "When used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written."
+            "value" : "In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written."
          }
       ]
    },
@@ -54,6 +54,8 @@
    "references" : {
       "reference_data" : [
          {
+            "name" : "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
+            "refsource" : "CONFIRM",
             "url" : "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/"
          }
       ]
diff --git a/2018/7xxx/CVE-2018-7166.json b/2018/7xxx/CVE-2018-7166.json
index feb8376a05b..ce347698917 100644
--- a/2018/7xxx/CVE-2018-7166.json
+++ b/2018/7xxx/CVE-2018-7166.json
@@ -35,7 +35,7 @@
       "description_data" : [
          {
             "lang" : "eng",
-            "value" : "An argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal \"fill\" method as the `start` to a fill operation. This flaw may be abused where `Buffer.alloc()` arguments are derived from user input to return uncleared memory blocks that may contain sensitive information."
+            "value" : "In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal \"fill\" method as the `start` to a fill operation. This flaw may be abused where `Buffer.alloc()` arguments are derived from user input to return uncleared memory blocks that may contain sensitive information."
          }
       ]
    },
@@ -54,6 +54,8 @@
    "references" : {
       "reference_data" : [
          {
+            "name" : "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
+            "refsource" : "CONFIRM",
             "url" : "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/"
          }
       ]