@storybook/addon-essentials provides a curated set of essential Storybook addons designed to enhance the developer experience and streamline the UI development workflow. Comparing versions 7.0.17 and 7.0.18, the core functionality remains consistent, focusing on providing tools for documentation, interaction, and visual debugging within Storybook. Both versions include dependencies like @storybook/addon-docs for generating documentation from stories, @storybook/addon-controls for interactive component property editing, and visual aid addons like @storybook/addon-measure, @storybook/addon-outline, @storybook/addon-backgrounds, and @storybook/addon-highlight for meticulous UI inspection.
A key aspect for developers is the consistent peer dependency requirements for React and React-DOM across versions, ensuring compatibility with a wide range of React projects. Furthermore, the consistent use of typescript and @storybook/vue as devDependencies highlights Storybook's commitment to supporting modern JavaScript and Vue.js development.
The primary difference between these versions lies in the internal updates and dependency alignment within the Storybook ecosystem. The upgrade from 7.0.17 to 7.0.18 involves synchronizing the versions of internal Storybook packages like @storybook/core-common, @storybook/manager-api, @storybook/preview-api, and others. While the exposed features and developer-facing API's provided by these addons remain the same, these updates likely address bug fixes, performance improvements, and dependency compatibility within the broader Storybook framework.
All the vulnerabilities related to the version 7.0.18 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.