Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 5 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,762exploited flaws on CISA’s list
34added in the last 30 days
344new WordPress flaws this week
390,080entries in the database

253 results · page 4 of 6

  • Aug 23, 2023A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x.CVE-2023-32559 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 21, 2023The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.CVE-2023-32002 · Other software · NodeJS · reported by support@hackerone.comCritical 9.8

    The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 16, 2023Jenkins NodeJS Plugin 1.6.0 and earlier does not properly mask (i.e., replace with asterisks) credentials specified in the Npm config file in Pipeline build logCVE-2023-40340 · Websites & servers · Jenkins Project · reported by jenkinsci-cert@googlegroups.comHigh 7.5

    Jenkins NodeJS Plugin 1.6.0 and earlier does not properly mask (i.e., replace with asterisks) credentials specified in the Npm config file in Pipeline build logs.

    Product
    Jenkins NodeJS Plugin
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 15, 2023The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.CVE-2023-32006 · Other software · NodeJS · reported by support@hackerone.comHigh 8.8

    The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 15, 2023A vulnerability has been discovered in Node.js version 20, specifically within the experimental permission model.CVE-2023-32004 · Other software · NodeJS · reported by support@hackerone.comHigh 8.8

    A vulnerability has been discovered in Node.js version 20, specifically within the experimental permission model. This flaw relates to improper handling of Buffers in file system APIs causing a traversal path to bypass when verifying file permissions. This vulnerability affects all users using the experimental permission model in Node.js 20. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 15, 2023`fs.mkdtemp()` and `fs.mkdtempSync()` can be used to bypass the permission model check using a path traversal attack.CVE-2023-32003 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    `fs.mkdtemp()` and `fs.mkdtempSync()` can be used to bypass the permission model check using a path traversal attack. This flaw arises from a missing check in the fs.mkdtemp() API and the impact is a malicious actor could create an arbitrary directory. This vulnerability affects all users using the experimental permission model in Node.js 20. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 12, 2023The Syncfusion EJ2 Node File Provider 0102271 is vulnerable to filesystem-server.js directory traversal.CVE-2023-26563 · Other software · Syncfusion · reported by MITRECritical 9.8

    The Syncfusion EJ2 Node File Provider 0102271 is vulnerable to filesystem-server.js directory traversal. As a result, an unauthenticated attacker can: - On Windows, list files in any directory, read any file, delete any file, upload any file to any directory accessible by the web server. - On Linux, read any file, download any directory, delete any file, upload any file to any directory accessible by the web server.

    Product
    Nodejs File System Provider
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 30, 2023The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests.CVE-2023-30589 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 30, 2023A privilege escalation vulnerability exists in Node.js 20 that allowed loading arbitrary OpenSSL engines when the experimental permission model is enabled, whicCVE-2023-30586 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    A privilege escalation vulnerability exists in Node.js 20 that allowed loading arbitrary OpenSSL engines when the experimental permission model is enabled, which can bypass and/or disable the permission model. The attack complexity is high. However, the crypto.setEngine() API can be used to bypass the permission model when called with a compatible OpenSSL engine. The OpenSSL engine can, for example, disable the permission model in the host process by manipulating the process's stack memory to locate the permission model Permission::enabled_ in the host process's heap memory. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 8, 2023snowflake-connector-nodejs, a NodeJS driver for Snowflake, is vulnerable to command injection via single sign on (SSO) browser URL authentication in versions prCVE-2023-34232 · Other software · snowflakedb · reported by GitHubHigh 7.3

    snowflake-connector-nodejs, a NodeJS driver for Snowflake, is vulnerable to command injection via single sign on (SSO) browser URL authentication in versions prior to 1.6.21. In order to exploit the potential for command injection, an attacker would need to be successful in (1) establishing a malicious resource and (2) redirecting users to utilize the resource. The attacker could set up a malicious, publicly accessible server which responds to the SSO URL with an attack payload. If the attacker then tricked a user into visiting the maliciously crafted connection URL, the user’s local machine would render the malicious payload, leading to a remote code execution. This attack scenario can be mitigated through URL whitelisting as well as common anti-phishing resources. Version 1.6.21 contains a patch for this issue.

    Product
    snowflake-connector-nodejs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 23, 2023An untrusted search path vulnerability exists in Node.js.CVE-2023-23920 · Other software · NodeJS · reported by support@hackerone.comMedium 4.2

    An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 23, 2023A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operatCVE-2023-23919 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set it. This may lead to false positive errors during subsequent cryptographic operations that happen to be on the same thread. This in turn could be used to cause a denial of service.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 23, 2023A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experimental Permissions (htCVE-2023-23918 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experimental Permissions (https://nodejs.org/api/permissions.html) feature in Node.js and access non authorized modules by using process.mainModule.require(). This only affects users who had enabled the experimental permissions option with --experimental-policy.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 16, 2023Undici is an HTTP/1.1 client for Node.js.CVE-2023-24807 · Other software · nodejs · reported by GitHubHigh 7.5

    Undici is an HTTP/1.1 client for Node.js. Prior to version 5.19.1, the `Headers.set()` and `Headers.append()` methods are vulnerable to Regular Expression Denial of Service (ReDoS) attacks when untrusted values are passed into the functions. This is due to the inefficient regular expression used to normalize the values in the `headerValueNormalize()` utility function. This vulnerability was patched in v5.19.1. No known workarounds are available.

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 16, 2023Undici is an HTTP/1.1 client for Node.js.CVE-2023-23936 · Other software · nodejs · reported by GitHubMedium 6.5

    Undici is an HTTP/1.1 client for Node.js. Starting with version 2.0.0 and prior to version 5.19.1, the undici library does not protect `host` HTTP header from CRLF injection vulnerabilities. This issue is patched in Undici v5.19.1. As a workaround, sanitize the `headers.host` string before passing to undici.

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 5, 2022A OS Command Injection vulnerability exists in Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 due to an insufficient IsAllowedHost check that can easilyCVE-2022-43548 · Other software · NodeJS · reported by support@hackerone.comHigh 8.1

    A OS Command Injection vulnerability exists in Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 due to an insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid before making DBS requests allowing rebinding attacks.The fix for this issue in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32212 was incomplete and this new CVE is to complete the fix.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 5, 2022The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF.CVE-2022-35256 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 5, 2022A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crCVE-2022-35255 · Other software · NodeJS · reported by support@hackerone.comCritical 9.1

    A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. There are two problems with this: 1) It does not check the return value, it assumes EntropySource() always succeeds, but it can (and sometimes will) fail. 2) The random data returned byEntropySource() may not be cryptographically strong and therefore not suitable as keying material.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2022isolated-vm is a library for nodejs which gives the user access to v8's Isolate interface.CVE-2022-39266 · Other software · laverdet · reported by GitHubCritical 9.6

    isolated-vm is a library for nodejs which gives the user access to v8's Isolate interface. In versions 4.3.6 and prior, if the untrusted v8 cached data is passed to the API through CachedDataOptions, attackers can bypass the sandbox and run arbitrary code in the nodejs process. Version 4.3.7 changes the documentation to warn users that they should not accept `cachedData` payloads from a user.

    Product
    isolated-vm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 15, 2022undici is an HTTP/1.1 client, written from scratch for Node.js.`=< undici@5.8.0` users are vulnerable to _CRLF Injection_ on headers when using unsanitized inpuCVE-2022-35948 · Other software · nodejs · reported by GitHubMedium 5.3

    undici is an HTTP/1.1 client, written from scratch for Node.js.`=< undici@5.8.0` users are vulnerable to _CRLF Injection_ on headers when using unsanitized input as request headers, more specifically, inside the `content-type` header. Example: ``` import { request } from 'undici' const unsanitizedContentTypeInput = 'application/json\r\n\r\nGET /foo2 HTTP/1.1' await request('http://localhost:3000, { method: 'GET', headers: { 'content-type': unsanitizedContentTypeInput }, }) ``` The above snippet will perform two requests in a single `request` API call: 1) `http://localhost:3000/` 2) `http://localhost:3000/foo2` This issue was patched in Undici v5.8.1. Sanitize input when sending content-type headers using user input as a workaround.

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 12, 2022undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user CVE-2022-35949 · Other software · nodejs · reported by GitHubMedium 5.3

    undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `http://127.0.0.1` or `//127.0.0.1` ```js const undici = require("undici") undici.request({origin: "http://example.com", pathname: "//127.0.0.1"}) ``` Instead of processing the request as `http://example.org//127.0.0.1` (or `http://example.org/http://127.0.0.1` when `http://127.0.0.1 is used`), it actually processes the request as `http://127.0.0.1/` and sends it to `http://127.0.0.1`. If a developer passes in user input into `path` parameter of `undici.request`, it can result in an _SSRF_ as they will assume that the hostname cannot change, when in actual fact it can change because the specified path parameter is combined with the base URL. This issue was fixed in `undici@5.8.1`. The best workaround is to validate user input before passing it to the `undici.request` call.

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2022Authorization headers are cleared on cross-origin redirect.CVE-2022-31151 · Other software · nodejs · reported by GitHubLow 3.7

    Authorization headers are cleared on cross-origin redirect. However, cookie headers which are sensitive headers and are official headers found in the spec, remain uncleared. There are active users using cookie headers in undici. This may lead to accidental leakage of cookie to a 3rd-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the 3rd party site. This was patched in v5.7.1. By default, this vulnerability is not exploitable. Do not enable redirections, i.e. `maxRedirections: 0` (the default).

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 19, 2022undici is an HTTP/1.1 client, written from scratch for Node.js.CVE-2022-31150 · Other software · nodejs · reported by GitHubMedium 5.3

    undici is an HTTP/1.1 client, written from scratch for Node.js. It is possible to inject CRLF sequences into request headers in undici in versions less than 5.7.1. A fix was released in version 5.8.0. Sanitizing all HTTP headers from untrusted sources to eliminate `\r\n` is a workaround for this issue.

    Product
    undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 18, 2022A vulnerability in Apache SkyWalking NodeJS Agent prior to 0.5.1.CVE-2022-36127 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 7.5

    A vulnerability in Apache SkyWalking NodeJS Agent prior to 0.5.1. The vulnerability will cause NodeJS services that has this agent installed to be unavailable if the OAP is unhealthy and NodeJS agent can't establish the connection.

    Product
    Apache SkyWalking NodeJS Agent
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim haCVE-2022-32223 · Other software · NodeJS · reported by support@hackerone.comHigh 7.3

    Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows machine:* OpenSSL has been installed and “C:\Program Files\Common Files\SSL\openssl.cnf” exists.Whenever the above conditions are present, `node.exe` will search for `providers.dll` in the current user directory.After that, `node.exe` will try to search for `providers.dll` by the DLL Search Order in Windows.It is possible for an attacker to place the malicious file `providers.dll` under a variety of paths and exploit this vulnerability.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be accessiCVE-2022-32222 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be accessible under some circumstances to a non-admin user instead of /etc/ssl as was the case in versions prior to the upgrade to OpenSSL 3.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers.CVE-2022-32215 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests.CVE-2022-32214 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead tCVE-2022-32213 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an insufficient IsAllowedHost check that can easily be bypassCVE-2022-32212 · Other software · NodeJS · reported by support@hackerone.comHigh 8.1

    A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid before making DBS requests allowing rebinding attacks.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2022`Undici.ProxyAgent` never verifies the remote server's certificate, and always exposes all request & response data to the proxy.CVE-2022-32210 · Other software · Nodejs · reported by support@hackerone.comMedium 6.5

    `Undici.ProxyAgent` never verifies the remote server's certificate, and always exposes all request & response data to the proxy. This unexpectedly means that proxies can MitM all HTTPS traffic, and if the proxy's URL is HTTP then it also means that nominally HTTPS requests are actually sent via plain-text HTTP between Undici and the proxy server.

    Product
    Undici
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 15, 2022NestJS Proxy is a NestJS module to decorate and proxy calls.CVE-2022-31070 · Other software · Finastra · reported by GitHubMedium 5.8

    NestJS Proxy is a NestJS module to decorate and proxy calls. Prior to version 0.7.0, the nestjs-proxy library did not have a way to block sensitive cookies (e.g. session cookies) from being forwarded to backend services configured by the application developer. This could have led to sensitive cookies being inadvertently exposed to such services that should not see them. The patched version now blocks cookies from being forwarded by default. However developers can configure an allow-list of cookie names by using the `allowedCookies` config setting. This issue has been fixed in version 0.7.0 of `@finastra/nestjs-proxy`. Users of `@ffdc/nestjs-proxy` are advised that this package has been deprecated and is no longer being maintained or receiving updates. Such users should update their package.json file to use `@finastra/nestjs-proxy` instead.

    Product
    finastra-nodejs-libs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 15, 2022NestJS Proxy is a NestJS module to decorate and proxy calls.CVE-2022-31069 · Other software · Finastra · reported by GitHubMedium 5.8

    NestJS Proxy is a NestJS module to decorate and proxy calls. Prior to version 0.7.0, the nestjs-proxy library did not have a way to control when Authorization headers should should be forwarded for specific backend services configured by the application developer. This could have resulted in sensitive information such as OAuth bearer access tokens being inadvertently exposed to such services that should not see them. A new feature has been introduced in the patched version of nestjs-proxy that allows application developers to opt out of forwarding the Authorization headers on a per service basis using the `forwardToken` config setting. Developers are advised to review the README for this library on Github or NPM for further details on how this configuration can be applied. This issue has been fixed in version 0.7.0 of `@finastra/nestjs-proxy`. Users of `@ffdc/nestjs-proxy` are advised that this package has been deprecated and is no longer being maintained or receiving updates. Such users should update their package.json file to use `@finastra/nestjs-proxy` instead.

    Product
    finastra-nodejs-libs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 24, 2022Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while siCVE-2022-21824 · Other software · NodeJS · reported by support@hackerone.comHigh 8.2

    Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be "__proto__". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object these properties are being assigned to.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 24, 2022Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly.CVE-2021-44533 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 24, 2022Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format.CVE-2021-44532 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 24, 2022Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrCVE-2021-44531 · Other software · NodeJS · reported by support@hackerone.comHigh 7.4

    Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 15, 2021The parser in accepts requests with a space (SP) right after the header name before the colon.CVE-2021-22959 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 3, 2021The parse function in llhttp < 2.1.4 and < 6.0.6.CVE-2021-22960 · Other software · NodeJS · reported by support@hackerone.comMedium 6.5

    The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 7, 2021Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to changeCVE-2021-22930 · Other software · NodeJS · reported by support@hackerone.comCritical 9.8

    Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 15, 2021nodejs-tmpl is vulnerable to Inefficient Regular Expression ComplexityCVE-2021-3777 · Other software · daaku · reported by security@huntr.devHigh 7.5

    nodejs-tmpl is vulnerable to Inefficient Regular Expression Complexity

    Product
    daaku/nodejs-tmpl
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 7, 2021remark-html is an open source nodejs library which compiles Markdown to HTML.CVE-2021-39199 · Other software · remarkjs · reported by GitHubCritical 10

    remark-html is an open source nodejs library which compiles Markdown to HTML. In affected versions the documentation of remark-html has mentioned that it was safe by default. In practice the default was never safe and had to be opted into. That is, user input was not sanitized. This means arbitrary HTML can be passed through leading to potential XSS attacks. The problem has been patched in 13.0.2 and 14.0.1: `remark-html` is now safe by default, and the implementation matches the documentation. On older affected versions, pass `sanitize: true` if you cannot update.

    Product
    remark-html
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 16, 2021Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to changeCVE-2021-22940 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 16, 2021If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to serCVE-2021-22939 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 16, 2021Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names returCVE-2021-22931 · Other software · NodeJS · reported by support@hackerone.comCritical 9.8

    Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 12, 2021Node.js before 16.4.1, 14.17.2, and 12.22.2 is vulnerable to local privilege escalation attacks under certain conditions on Windows platforms.CVE-2021-22921 · Other software · NodeJS · reported by support@hackerone.comHigh 7.8

    Node.js before 16.4.1, 14.17.2, and 12.22.2 is vulnerable to local privilege escalation attacks under certain conditions on Windows platforms. More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different escalation attacks: PATH and DLL hijacking.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 12, 2021Node.js before 16.4.1, 14.17.2, 12.22.2 is vulnerable to an out-of-bounds read when uv__idna_toascii() is used to convert strings to ASCII.CVE-2021-22918 · Other software · NodeJS · reported by support@hackerone.comMedium 5.3

    Node.js before 16.4.1, 14.17.2, 12.22.2 is vulnerable to an out-of-bounds read when uv__idna_toascii() is used to convert strings to ASCII. The pointer p is read and increased without checking whether it is beyond pe, with the latter holding a pointer to the end of the buffer. This can lead to information disclosures or crashes. This function can be triggered via uv_getaddrinfo().

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 1, 2021node-etsy-client is a NodeJs Etsy ReST API Client.CVE-2021-21421 · Other software · creharmony · reported by GitHubHigh 8.1

    node-etsy-client is a NodeJs Etsy ReST API Client. Applications that are using node-etsy-client and reporting client error to the end user will offer api key value too This is fixed in node-etsy-client v0.3.0 and later.

    Product
    node-etsy-client
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 30, 2021isolated-vm is a library for nodejs which gives you access to v8's Isolate interface.CVE-2021-21413 · Other software · laverdet · reported by GitHubHigh 8

    isolated-vm is a library for nodejs which gives you access to v8's Isolate interface. Versions of isolated-vm before v4.0.0 have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate. Reference objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a Reference instance to an attacker they would be able to use it to acquire a Reference to the nodejs context's Function object. Similar application-specific attacks could be possible by modifying the local prototype of other API objects. Access to NativeModule objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution. This is addressed in v4.0.0 through a series of related changes.

    Product
    isolated-vm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 3, 2021Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”.CVE-2021-22884 · Other software · NodeJS · reported by support@hackerone.comHigh 7.5

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160.

    Product
    Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.