ghsa-6v28-c2x2-8p46
Vulnerability from github
Published
2022-05-13 01:16
Modified
2022-05-13 01:16
Severity ?
Details
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.
{ "affected": [], "aliases": [ "CVE-2018-7166" ], "database_specific": { "cwe_ids": [ "CWE-908" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2018-08-21T12:29:00Z", "severity": "HIGH" }, "details": "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\u0027s` 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.", "id": "GHSA-6v28-c2x2-8p46", "modified": "2022-05-13T01:16:08Z", "published": "2022-05-13T01:16:08Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-7166" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2018:2553" }, { "type": "WEB", "url": "https://nodejs.org/en/blog/vulnerability/august-2018-security-releases" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ] }
Loading...
Loading...
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.