Nodejs Node.js 5.1.0
Approved changes feed: RSS · Atom
cpe:2.3:a:nodejs:node.js:5.1.0:*:*:*:*:*:*:*
part: a version: 5.1.0 update: *
| Vendor | Nodejs (1eb6e5de-a495-50c0-9bb4-c8200a117578) |
|---|---|
| Product | Node.Js (35820ba0-265c-5d96-8f6e-66bb0af213e7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/nodejs |
purl2cpe | 2026-06-01 10:15:59.224674 |
pkg:deb/ubuntu/nodejs |
purl2cpe | 2026-06-01 10:15:59.224675 |
pkg:github/nodejs/node |
purl2cpe | 2026-06-01 10:15:59.224676 |
pkg:rpm/fedora/nodejs |
purl2cpe | 2026-06-01 10:15:59.224678 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-11499 |
vulnerable | 2026-06-08 05:08:37.921014 |
Details available
Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 through v7.10.0, and v8.0 through v8.1.3 was susceptible to hash flooding remote DoS attacks as the HashTable seed was constant across a given released version of Node.js. This was a result of building with V8 snapshots enabled by default which caused the initially randomized seed to be overwritten on startup.
Published: 2017-07-25T13:00:00.000Z
Updated: 2024-08-05T18:12:40.348Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-3956 |
vulnerable | 2026-06-08 05:07:46.303116 |
Details available
The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.
Published: 2016-07-02T14:00:00.000Z
Updated: 2024-08-06T00:10:31.975Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-2216 |
vulnerable | 2026-06-08 05:07:33.697640 |
Details available
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
Published: 2016-04-07T21:00:00.000Z
Updated: 2024-08-05T23:24:48.440Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-2086 |
vulnerable | 2026-06-08 05:07:32.884706 |
Details available
Node.js 0.10.x before 0.10.42, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allow remote attackers to conduct HTTP request smuggling attacks via a crafted Content-Length HTTP header.
Published: 2016-04-07T21:00:00.000Z
Updated: 2024-08-05T23:17:50.495Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-8027 |
vulnerable | 2026-06-08 05:07:02.947772 |
Details available
Node.js 0.12.x before 0.12.9, 4.x before 4.2.3, and 5.x before 5.1.1 does not ensure the availability of a parser for each HTTP socket, which allows remote attackers to cause a denial of service (uncaughtException and service outage) via a pipelined HTTP request.
Published: 2016-01-02T21:00:00.000Z
Updated: 2024-08-06T08:06:31.544Z Reference links
|
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.