CVE-2017-15897 (GCVE-0-2017-15897)

Vulnerability from cvelistv5 – Published: 2017-12-11 21:00 – Updated: 2024-09-17 03:42
VLAI
Summary
Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffer.alloc(0x100, "This is not correctly encoded", "hex");' The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.
Severity
3.1 (Low)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CWE
  • Un-initialized Data
Assigner
nodejs CNA under the mitre root
CNA scorecard – unranked: 0 records in the last 180 days, 10 needed details
References
Impacted products
Vendor Product Version CPE status
The Node.js Project Node.js Affected: 8.0 and higher
Affected: 9.0 and higher
guessed Create a notification for this product.
Date Public
2017-12-07 00:00
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T20:04:50.511Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Node.js",
          "vendor": "The Node.js Project",
          "versions": [
            {
              "status": "affected",
              "version": "8.0 and higher"
            },
            {
              "status": "affected",
              "version": "9.0 and higher"
            }
          ]
        }
      ],
      "datePublic": "2017-12-07T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, \u0027Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\u0027 The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Un-initialized Data",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-12-11T20:57:01.000Z",
        "orgId": "386269d4-a6c6-4eaa-bf8e-bc0b0d010558",
        "shortName": "nodejs"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve-request@iojs.org",
          "DATE_PUBLIC": "2017-12-07T00:00:00",
          "ID": "CVE-2017-15897",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Node.js",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "8.0 and higher"
                          },
                          {
                            "version_value": "9.0 and higher"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "The Node.js Project"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, \u0027Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\u0027 The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Un-initialized Data"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/",
              "refsource": "CONFIRM",
              "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "386269d4-a6c6-4eaa-bf8e-bc0b0d010558",
    "assignerShortName": "nodejs",
    "cveId": "CVE-2017-15897",
    "datePublished": "2017-12-11T21:00:00.000Z",
    "dateReserved": "2017-10-25T00:00:00.000Z",
    "dateUpdated": "2024-09-17T03:42:59.193Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2017-15897",
      "date": "2026-10-20",
      "epss": "0.02322",
      "percentile": "0.83233"
    },
    "fkie_nvd": {
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*",
                  "matchCriteriaId": "74FB695D-2C76-47AB-988E-5629D2E695E5",
                  "versionEndIncluding": "8.8.1",
                  "versionStartIncluding": "8.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*",
                  "matchCriteriaId": "C45E9D50-CD3D-480B-B9B8-451ADFF26505",
                  "versionEndExcluding": "8.9.3",
                  "versionStartIncluding": "8.9.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*",
                  "matchCriteriaId": "82FDBB10-3298-4C9A-9CC0-D34643AEC868",
                  "versionEndExcluding": "9.2.1",
                  "versionStartIncluding": "9.0.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, \u0027Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\u0027 The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases."
        },
        {
          "lang": "es",
          "value": "Node.js ten\u00eda un bug en las versiones 8.X y 9.X que provocaba que los b\u00fafers no se inicializasen cuando la codificaci\u00f3n para el valor de relleno no coincid\u00eda con la codificaci\u00f3n especificada. Por ejemplo, \"Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\" La implementaci\u00f3n del b\u00fafer se actualiz\u00f3 de tal forma que el b\u00fafer se inicializar\u00e1 con todo ceros en esos casos."
        }
      ],
      "id": "CVE-2017-15897",
      "lastModified": "2024-11-21T03:15:25.853",
      "metrics": {
        "cvssMetricV2": [
          {
            "acInsufInfo": false,
            "baseSeverity": "MEDIUM",
            "cvssData": {
              "accessComplexity": "MEDIUM",
              "accessVector": "NETWORK",
              "authentication": "NONE",
              "availabilityImpact": "NONE",
              "baseScore": 4.3,
              "confidentialityImpact": "PARTIAL",
              "integrityImpact": "NONE",
              "vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
              "version": "2.0"
            },
            "exploitabilityScore": 8.6,
            "impactScore": 2.9,
            "obtainAllPrivilege": false,
            "obtainOtherPrivilege": false,
            "obtainUserPrivilege": false,
            "source": "nvd@nist.gov",
            "type": "Primary",
            "userInteractionRequired": false
          }
        ],
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 3.1,
              "baseSeverity": "LOW",
              "confidentialityImpact": "LOW",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
              "version": "3.1"
            },
            "exploitabilityScore": 1.6,
            "impactScore": 1.4,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      },
      "published": "2017-12-11T21:29:00.563",
      "references": [
        {
          "source": "cve-request@iojs.org",
          "tags": [
            "Issue Tracking",
            "Vendor Advisory"
          ],
          "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Issue Tracking",
            "Vendor Advisory"
          ],
          "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
        }
      ],
      "sourceIdentifier": "cve-request@iojs.org",
      "vulnStatus": "Modified",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-665"
            }
          ],
          "source": "nvd@nist.gov",
          "type": "Primary"
        }
      ]
    },
    "nvd": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "74FB695D-2C76-47AB-988E-5629D2E695E5",
                    "versionEndIncluding": "8.8.1",
                    "versionStartIncluding": "8.0.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*",
                    "matchCriteriaId": "C45E9D50-CD3D-480B-B9B8-451ADFF26505",
                    "versionEndExcluding": "8.9.3",
                    "versionStartIncluding": "8.9.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "82FDBB10-3298-4C9A-9CC0-D34643AEC868",
                    "versionEndExcluding": "9.2.1",
                    "versionStartIncluding": "9.0.0",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, \u0027Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\u0027 The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases."
          },
          {
            "lang": "es",
            "value": "Node.js ten\u00eda un bug en las versiones 8.X y 9.X que provocaba que los b\u00fafers no se inicializasen cuando la codificaci\u00f3n para el valor de relleno no coincid\u00eda con la codificaci\u00f3n especificada. Por ejemplo, \"Buffer.alloc(0x100, \"This is not correctly encoded\", \"hex\");\" La implementaci\u00f3n del b\u00fafer se actualiz\u00f3 de tal forma que el b\u00fafer se inicializar\u00e1 con todo ceros en esos casos."
          }
        ],
        "id": "CVE-2017-15897",
        "lastModified": "2026-05-13T00:24:29.033",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "MEDIUM",
                "accessVector": "NETWORK",
                "authentication": "NONE",
                "availabilityImpact": "NONE",
                "baseScore": 4.3,
                "confidentialityImpact": "PARTIAL",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
                "version": "2.0"
              },
              "exploitabilityScore": 8.6,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 3.1,
                "baseSeverity": "LOW",
                "confidentialityImpact": "LOW",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 1.6,
              "impactScore": 1.4,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2017-12-11T21:29:00.563",
        "references": [
          {
            "source": "cve-request@iojs.org",
            "tags": [
              "Issue Tracking",
              "Vendor Advisory"
            ],
            "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Issue Tracking",
              "Vendor Advisory"
            ],
            "url": "https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/"
          }
        ],
        "sourceIdentifier": "cve-request@iojs.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-665"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-05-13T03:48:14+00:00",
      "cve": "CVE-2017-15897",
      "id": "CVE-2017-15897",
      "initial_release_date": "2017-12-07T00:00:00+00:00",
      "product_status:known_affected": "19",
      "product_status:known_not_affected": "18",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "nodejs: Unitialized buffer due to incorrect encoding",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2017/cve-2017-15897.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-31T08:57:33Z",
      "cve": "CVE-2017-15897",
      "id": "CVE-2017-15897",
      "initial_release_date": "2023-02-15T04:37:46Z",
      "product_status:known_not_affected": "326",
      "product_status:recommended": "143",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2017-15897",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2017-15897.json",
      "version": "20"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.