rpm package
suse/nodejs8&distro=SUSE Linux Enterprise Module for Web and Scripting 15 SP1
pkg:rpm/suse/nodejs8&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Web%20and%20Scripting%2015%20SP1
Vulnerabilities (19)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-8174 | Hig | 8.1 | < 8.17.0-3.32.1 | 8.17.0-3.32.1 | Jul 24, 2020 | napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0. | |
| CVE-2020-15095 | Med | 4.4 | < 8.17.0-3.38.1 | 8.17.0-3.38.1 | Jul 7, 2020 | Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "://[[:]@][:][:][/]". The password value is not redacted and is printed to stdout and also | |
| CVE-2020-11080 | Low | 3.7 | < 8.17.0-3.32.1 | 8.17.0-3.32.1 | Jun 3, 2020 | In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. T | |
| CVE-2020-7598 | Med | 5.6 | < 8.17.0-3.32.1 | 8.17.0-3.32.1 | Mar 11, 2020 | minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload. | |
| CVE-2019-15606 | Cri | 9.8 | < 8.17.0-3.28.1 | 8.17.0-3.28.1 | Feb 7, 2020 | Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons | |
| CVE-2019-15605 | Cri | 9.8 | < 8.17.0-3.28.1 | 8.17.0-3.28.1 | Feb 7, 2020 | HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed | |
| CVE-2019-15604 | Hig | 7.5 | < 8.17.0-3.28.1 | 8.17.0-3.28.1 | Feb 7, 2020 | Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificate | |
| CVE-2019-16777 | Hig | 7.7 | < 8.17.0-3.25.1 | 8.17.0-3.25.1 | Dec 13, 2019 | Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subse | |
| CVE-2019-16776 | Hig | 7.7 | < 8.17.0-3.25.1 | 8.17.0-3.25.1 | Dec 13, 2019 | Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher t | |
| CVE-2019-16775 | Hig | 7.7 | < 8.17.0-3.25.1 | 8.17.0-3.25.1 | Dec 13, 2019 | Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would a | |
| CVE-2019-9518 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. | |
| CVE-2019-9517 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually writ | |
| CVE-2019-9516 | Med | 6.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations a | |
| CVE-2019-9515 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame | |
| CVE-2019-9514 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer | |
| CVE-2019-9513 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consu | |
| CVE-2019-9512 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consum | |
| CVE-2019-9511 | Hig | 7.5 | < 8.16.1-3.20.1 | 8.16.1-3.20.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and | |
| CVE-2019-13173 | Hig | 7.5 | < 8.15.1-3.17.1 | 8.15.1-3.17.1 | Jul 2, 2019 | fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirW |
- affected < 8.17.0-3.32.1fixed 8.17.0-3.32.1
napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0.
- affected < 8.17.0-3.38.1fixed 8.17.0-3.38.1
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "://[[:]@][:][:][/]". The password value is not redacted and is printed to stdout and also
- affected < 8.17.0-3.32.1fixed 8.17.0-3.32.1
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. T
- affected < 8.17.0-3.32.1fixed 8.17.0-3.32.1
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
- affected < 8.17.0-3.28.1fixed 8.17.0-3.28.1
Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons
- affected < 8.17.0-3.28.1fixed 8.17.0-3.28.1
HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
- affected < 8.17.0-3.28.1fixed 8.17.0-3.28.1
Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificate
- affected < 8.17.0-3.25.1fixed 8.17.0-3.25.1
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subse
- affected < 8.17.0-3.25.1fixed 8.17.0-3.25.1
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher t
- affected < 8.17.0-3.25.1fixed 8.17.0-3.25.1
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would a
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE.
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually writ
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations a
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consu
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consum
- affected < 8.16.1-3.20.1fixed 8.16.1-3.20.1
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and
- affected < 8.15.1-3.17.1fixed 8.15.1-3.17.1
fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirW