You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the Host header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a /. This vulnerability was fixed in Next.js 14.1.1.
Prior to versions 7.1.0, 6.1.2, and 5.3.4, the webpack-dev-middleware development middleware for devpack does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine. The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory memfs filesystem. If writeToDisk configuration option is set to true, the physical filesystem is used. The getFilenameFromUrl method is used to parse URL and build the local file path. The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the outputPath. As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use %2e and %2f sequences to perform path traversal attack.
Developers using webpack-dev-server or webpack-dev-middleware are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content. If the development server is listening on a public IP address (or 0.0.0.0), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port). If the server allows access from third-party domains, an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files. Starting with fixed versions 7.1.0, 6.1.2, and 5.3.4, the URL is unescaped and normalized before any further processing.
mend-bolt-for-githubbot
changed the title
next-18.0.4.tgz: 1 vulnerabilities (highest severity is: 7.4)
next-18.0.4.tgz: 2 vulnerabilities (highest severity is: 7.5)
May 10, 2024
mend-bolt-for-githubbot
changed the title
next-18.0.4.tgz: 2 vulnerabilities (highest severity is: 7.5)
next-18.0.4.tgz: 3 vulnerabilities (highest severity is: 7.5)
Jul 2, 2024
mend-bolt-for-githubbot
changed the title
next-18.0.4.tgz: 3 vulnerabilities (highest severity is: 7.5)
next-18.0.4.tgz: 2 vulnerabilities (highest severity is: 7.5)
Jul 18, 2024
Vulnerable Library - next-18.0.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-34351
Vulnerable Library - next-14.0.4.tgz
Library home page: https://registry.npmjs.org/next/-/next-14.0.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the
Host
header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a/
. This vulnerability was fixed in Next.js14.1.1
.Publish Date: 2024-05-09
URL: CVE-2024-34351
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-77r5-gw3j-2mpf
Release Date: 2024-05-09
Fix Resolution (next): 14.1.1-canary.0
Direct dependency fix Resolution (@nx/next): 18.0.5
Step up your Open Source Security Game with Mend here
CVE-2024-29180
Vulnerable Library - webpack-dev-middleware-5.3.3.tgz
A development middleware for webpack
Library home page: https://registry.npmjs.org/webpack-dev-middleware/-/webpack-dev-middleware-5.3.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Prior to versions 7.1.0, 6.1.2, and 5.3.4, the webpack-dev-middleware development middleware for devpack does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine. The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory
memfs
filesystem. IfwriteToDisk
configuration option is set totrue
, the physical filesystem is used. ThegetFilenameFromUrl
method is used to parse URL and build the local file path. The public path prefix is stripped from the URL, and theunsecaped
path suffix is appended to theoutputPath
. As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use%2e
and%2f
sequences to perform path traversal attack.Developers using
webpack-dev-server
orwebpack-dev-middleware
are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content. If the development server is listening on a public IP address (or0.0.0.0
), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port). If the server allows access from third-party domains, an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files. Starting with fixed versions 7.1.0, 6.1.2, and 5.3.4, the URL is unescaped and normalized before any further processing.Publish Date: 2024-03-21
URL: CVE-2024-29180
CVSS 3 Score Details (7.4)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-wr3j-pwj9-hqq6
Release Date: 2024-03-21
Fix Resolution (webpack-dev-middleware): 5.3.4
Direct dependency fix Resolution (@nx/next): 18.0.5
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: