Tsx is a powerful tool for Node.js developers, enabling seamless execution of TypeScript and ESM files directly, leveraging the speed and efficiency of esbuild. Versions 4.15.8 and 4.15.9 are both recent releases of this popular package, offering similar core functionality for streamlined TypeScript development.
Examining the provided data, the differences between tsx 4.15.8 and tsx 4.15.9 appear minimal but potentially impactful. Both versions share identical dependencies on esbuild (version ~0.21.4) and get-tsconfig (version ^4.7.5), along with the optional dependency fsevents (version ~2.3.3). They are authored by Hiroki Osame and licensed under MIT. The file count in the dist is the same and the unpackedSize has a minimal difference of 26 bytes
The key distinction lies in the releaseDate. Version 4.15.9 was published on June 29, 2024, while 4.15.8 was released on June 28, 2024. While the dependencies remained the same, this likely means that 4.15.9 has a set of small bug fixes compared to 4.15.8
For developers, upgrading to tsx 4.15.9 is typically recommended to benefit from the latest improvements and potential bug fixes. given the similarities, the upgrade should be seamless. Tsx simplifies TypeScript execution, supporting modern ECMAScript modules and accelerating development workflows by eliminating the need for manual compilation steps.
All the vulnerabilities related to the version 4.15.9 of the package
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: * header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com).fetch('http://127.0.0.1:8000/main.js') request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html: normally you have a script tag here/assets: it's common to have a assets directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data)))The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm inpm run watchfetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.