gsd-2018-12115
Vulnerability from gsd
Modified
2023-12-13 01:22
Details
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.
Aliases
Aliases
CVE-2018-12115


To clipboard 

{
   GSD: {
      alias: "CVE-2018-12115",
      description: "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.",
      id: "GSD-2018-12115",
      references: [
         "https://www.suse.com/security/cve/CVE-2018-12115.html",
         "https://access.redhat.com/errata/RHSA-2018:3537",
         "https://access.redhat.com/errata/RHSA-2018:2949",
         "https://access.redhat.com/errata/RHSA-2018:2944",
         "https://access.redhat.com/errata/RHSA-2018:2553",
         "https://access.redhat.com/errata/RHSA-2018:2552",
         "https://advisories.mageia.org/CVE-2018-12115.html",
         "https://ubuntu.com/security/CVE-2018-12115",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2018-12115",
         ],
         details: "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.",
         id: "GSD-2018-12115",
         modified: "2023-12-13T01:22:29.724353Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "cve-request@iojs.org",
            DATE_PUBLIC: "2018-08-12T00:00:00",
            ID: "CVE-2018-12115",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "Node.js",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "All versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "The Node.js Project",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  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.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "CWE-787: Out-of-bounds Write",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "105127",
                  refsource: "BID",
                  url: "http://www.securityfocus.com/bid/105127",
               },
               {
                  name: "RHSA-2018:2552",
                  refsource: "REDHAT",
                  url: "https://access.redhat.com/errata/RHSA-2018:2552",
               },
               {
                  name: "RHSA-2018:2553",
                  refsource: "REDHAT",
                  url: "https://access.redhat.com/errata/RHSA-2018:2553",
               },
               {
                  name: "RHSA-2018:2944",
                  refsource: "REDHAT",
                  url: "https://access.redhat.com/errata/RHSA-2018:2944",
               },
               {
                  name: "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
                  refsource: "CONFIRM",
                  url: "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
               },
               {
                  name: "RHSA-2018:3537",
                  refsource: "REDHAT",
                  url: "https://access.redhat.com/errata/RHSA-2018:3537",
               },
               {
                  name: "RHSA-2018:2949",
                  refsource: "REDHAT",
                  url: "https://access.redhat.com/errata/RHSA-2018:2949",
               },
               {
                  name: "GLSA-202003-48",
                  refsource: "GENTOO",
                  url: "https://security.gentoo.org/glsa/202003-48",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndExcluding: "8.11.4",
                        versionStartIncluding: "8.0.0",
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndExcluding: "10.9.0",
                        versionStartIncluding: "10.0.0",
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndExcluding: "6.14.4",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "cve-request@iojs.org",
               ID: "CVE-2018-12115",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     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.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-787",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
                     refsource: "CONFIRM",
                     tags: [
                        "Vendor Advisory",
                     ],
                     url: "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/",
                  },
                  {
                     name: "RHSA-2018:2553",
                     refsource: "REDHAT",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://access.redhat.com/errata/RHSA-2018:2553",
                  },
                  {
                     name: "RHSA-2018:2552",
                     refsource: "REDHAT",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://access.redhat.com/errata/RHSA-2018:2552",
                  },
                  {
                     name: "105127",
                     refsource: "BID",
                     tags: [
                        "Third Party Advisory",
                        "VDB Entry",
                     ],
                     url: "http://www.securityfocus.com/bid/105127",
                  },
                  {
                     name: "RHSA-2018:2944",
                     refsource: "REDHAT",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://access.redhat.com/errata/RHSA-2018:2944",
                  },
                  {
                     name: "RHSA-2018:2949",
                     refsource: "REDHAT",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://access.redhat.com/errata/RHSA-2018:2949",
                  },
                  {
                     name: "RHSA-2018:3537",
                     refsource: "REDHAT",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://access.redhat.com/errata/RHSA-2018:3537",
                  },
                  {
                     name: "GLSA-202003-48",
                     refsource: "GENTOO",
                     tags: [],
                     url: "https://security.gentoo.org/glsa/202003-48",
                  },
               ],
            },
         },
         impact: {
            baseMetricV2: {
               acInsufInfo: false,
               cvssV2: {
                  accessComplexity: "LOW",
                  accessVector: "NETWORK",
                  authentication: "NONE",
                  availabilityImpact: "PARTIAL",
                  baseScore: 5,
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  vectorString: "AV:N/AC:L/Au:N/C:N/I:N/A:P",
                  version: "2.0",
               },
               exploitabilityScore: 10,
               impactScore: 2.9,
               obtainAllPrivilege: false,
               obtainOtherPrivilege: false,
               obtainUserPrivilege: false,
               severity: "MEDIUM",
               userInteractionRequired: false,
            },
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "HIGH",
                  baseScore: 7.5,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                  version: "3.0",
               },
               exploitabilityScore: 3.9,
               impactScore: 3.6,
            },
         },
         lastModifiedDate: "2020-03-20T21:15Z",
         publishedDate: "2018-08-21T12:29Z",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.