Approved changes feed: RSS · Atom
cpe:2.3:a:the_node.js_project:node.js:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | The Node.Js Project (4fe151b1-7375-581d-bb89-2e7b34ae01ce) |
|---|---|
| Product | Node.Js (6537b69a-0aae-5d35-b628-9e50168d3c3f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-7167 |
vulnerable | 2026-06-08 05:11:55.074724 |
Details available
Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of Node.js 6.x (LTS "Boron"), 8.x (LTS "Carbon"), and 9.x are vulnerable. All versions of Node.js 10.x (Current) are NOT vulnerable.
Published: 2018-06-13T16:00:00.000Z
Updated: 2026-10-08T21:14:04.882Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7166 |
vulnerable | 2026-06-08 05:11:55.074384 |
Details available
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.
Published: 2018-08-21T13:00:00.000Z
Updated: 2026-10-08T21:14:05.567Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7164 |
vulnerable | 2026-06-08 05:11:55.074051 |
Details available
Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM. A bug introduced in 9.7.0 increases the memory consumed when reading from the network into JavaScript using the net.Socket object directly as a stream. An attacker could use this cause a denial of service by sending tiny chunks of data in short succession. This vulnerability was restored by reverting to the prior behaviour.
Published: 2018-06-13T16:00:00.000Z
Updated: 2026-10-08T21:14:05.436Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7162 |
vulnerable | 2026-06-08 05:11:55.073712 |
Details available
All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node process which provides an http server supporting TLS server to crash. This can be accomplished by sending duplicate/unexpected messages during the handshake. This vulnerability has been addressed by updating the TLS implementation.
Published: 2018-06-13T16:00:00.000Z
Updated: 2026-10-08T21:14:04.752Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7161 |
vulnerable | 2026-06-08 05:11:55.073353 |
Details available
All versions of Node.js 8.x, 9.x, and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node server providing an http2 server to crash. This can be accomplished by interacting with the http2 server in a manner that triggers a cleanup bug where objects are used in native code after they are no longer available. This has been addressed by updating the http2 implementation.
Published: 2018-06-13T16:00:00.000Z
Updated: 2026-10-08T21:14:04.606Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7160 |
vulnerable | 2026-06-08 05:11:55.072665 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7159 |
vulnerable | 2026-06-08 05:11:55.072104 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7158 |
vulnerable | 2026-06-08 05:11:55.070398 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12123 |
vulnerable | 2026-06-08 05:10:39.863758 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12122 |
vulnerable | 2026-06-08 05:10:39.863064 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12121 |
vulnerable | 2026-06-08 05:10:39.854053 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12120 |
vulnerable | 2026-06-08 05:10:39.853548 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12116 |
vulnerable | 2026-06-08 05:10:39.848758 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-12115 |
vulnerable | 2026-06-08 05:10:39.847693 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-15897 |
vulnerable | 2026-06-08 05:08:59.687394 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-15896 |
vulnerable | 2026-06-08 05:08:59.685848 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.