Ts-jest version 27.1.0 is a minor update to the popular Jest transformer, building upon the foundation laid by version 27.0.7. Both versions enable developers to seamlessly test TypeScript projects using Jest, providing source map support for easier debugging.
Key differences emerge in the dependency landscape. Version 27.1.0 introduces esbuild as a dependency, pegged to version ~0.14.0, potentially improving build speed and offering alternative transformation capabilities. It also upgrades @typescript-eslint/parser and @typescript-eslint/eslint-plugin to version ^5.3.0 from 4.x in the previous release, meaning better linting and code analysis for modern TypeScript features. Jest dependency in devDependencies is moved to ^27.4.3 from ^27.1.1. @jest/types is updated accordingly, from version ^27.1.1 to ^27.4.2. Also, typescript version is updated from ~4.2.4 to ~4.5.2. It's worth noting the removal of the source-map devDependency in 27.1.0 and the addition of several new @types devDependencies to improve type safety, such as @types/cross-spawn and @types/yargs-parser. @commitlint/cli and @commitlint/config-angular have both been upgraded from 13.x to 15.x.
For developers using ts-jest, these changes suggest incremental improvements in tooling and dependency management. The addition of esbuild *might* translate to faster transformations, but developers may notice benefits in code analysis through the upgraded typescript, eslint and related packages. Before upgrading, developers should check the changelog.
All the vulnerabilities related to the version 27.1.0 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.