Serve-static is a valuable npm package for serving static files in web applications, particularly when working with Express.js. Examining versions 1.12.0 and 1.12.1 reveals subtle but noteworthy changes for developers. The core functionality remains consistent, focusing on efficiently delivering static assets like HTML, CSS, JavaScript, and images. A key difference lies in the updated dependency on the send package, moving from version 0.15.0 to 0.15.1. This likely incorporates bug fixes or minor improvements within the send module, which handles the file sending process.
Furthermore, the development environment saw updates. Version 1.12.1 features newer versions of several development dependencies, including eslint (3.17.0 vs 3.16.1), eslint-plugin-promise (3.5.0 vs 3.4.0), eslint-config-standard (7.0.0 vs 6.2.1), eslint-plugin-markdown (1.0.0-beta.4 vs 1.0.0-beta.3), and eslint-plugin-standard (2.1.1 vs 2.0.1). These updates suggest a focus on code quality and adherence to modern JavaScript standards. Developers contributing to or extending serve-static will appreciate these refinements in the linting and testing setup. For those simply using the package to serve static files, the impact should be minimal, primarily manifested as potentially more robust and reliable underlying file delivery mechanisms courtesy of send update.
All the vulnerabilities related to the version 1.12.1 of the package
serve-static vulnerable to template injection that can lead to XSS
passing untrusted user input - even after sanitizing it - to redirect() may execute untrusted code
this issue is patched in serve-static 1.16.0
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
successful exploitation of this vector requires the following:
send vulnerable to template injection that can lead to XSS
passing untrusted user input - even after sanitizing it - to SendStream.redirect() may execute untrusted code
this issue is patched in send 0.19.0
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
successful exploitation of this vector requires the following:
Vercel ms Inefficient Regular Expression Complexity vulnerability
A vulnerability, which was classified as problematic, has been found in vercel ms up to 1.x. This issue affects the function parse of the file index.js. The manipulation of the argument str leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is caae2988ba2a37765d055c4eee63d383320ee662. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217451.
mime Regular Expression Denial of Service when MIME lookup performed on untrusted user input
Affected versions of mime are vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
Update to version 2.0.3 or later.
debug Inefficient Regular Expression Complexity vulnerability
A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The name of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability. The patch has been backported to the 2.6.x branch in version 2.6.9.
Regular Expression Denial of Service in debug
Affected versions of debug are vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter.
As it takes 50,000 characters to block the event loop for 2 seconds, this issue is a low severity issue.
This was later re-introduced in version v3.2.0, and then repatched in versions 3.2.7 and 4.3.1.
Version 2.x.x: Update to version 2.6.9 or later. Version 3.1.x: Update to version 3.1.0 or later. Version 3.2.x: Update to version 3.2.7 or later. Version 4.x.x: Update to version 4.3.1 or later.
Regular Expression Denial of Service in fresh
Affected versions of fresh are vulnerable to regular expression denial of service when parsing specially crafted user input.
Update to version 0.5.2 or later.
