Version Details and Security Vulnerabilities

📦

esbuild

0.2.10

Comparision Betweeen 0.2.10 and 0.2.9

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

18.33 KB

Version 0.2.10 Details

Esbuild versions 0.2.9 and 0.2.10 are both iterations of an extremely fast JavaScript bundler and minifier designed to optimize web development workflows. Both versions share the same core description, license (MIT), and repository details, indicating a consistent project philosophy. The core functionality remains centered around providing developers with a speedy and efficient tool for bundling and minifying JavaScript code, a crucial step in modern web development for improving website performance.

The key difference between the two versions lies in their release dates and potentially any underlying bug fixes or minor improvements. Version 0.2.10 was released on May 9, 2020, while version 0.2.9 was released on May 8, 2020. The unpacked size of version 0.2.10 is 18774 bytes, a negligible increase of 1 byte compared to version 0.2.9 (18773 bytes), implying very minimal changes in the codebase. For developers, this suggests that upgrading from 0.2.9 to 0.2.10 should be a seamless process with minimal risk of breaking changes. Despite the minor nature of the update, it's always recommended to review the changelog to confirm if any specific bug fixes or enhancements address particular issues encountered in the previous version. Developers benefit from esbuild’s speed and efficiency, streamlining their development process and resulting in faster website load times for end-users. Regular updates, even incremental ones, help ensure a reliable and performant bundling experience.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.

Version Details and Security Vulnerabilities

📦

esbuild

0.2.10

Comparision Betweeen 0.2.10 and 0.2.9

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

18.33 KB

Version 0.2.10 Details

Security Vulnerabilities

Security Details

Comprehensive list of direct or transitive vulnerabilities for version 0.2.10 of the package esbuild.

All Security Vulnerabilities

All the vulnerabilities related to the version 0.2.10 of the package

Summary:

esbuild enables any website to send any requests to the development server and read the response

Details:

Summary

esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.

Details

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:

The attacker serves a malicious web page (http://malicious.example.com).
The user accesses the malicious web page.
The attacker sends a 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.
The attacker gets the content of 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

Fetching /index.html: normally you have a script tag here
Fetching /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
Connecting /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)))
Fetching URLs in the known file: once the attacker knows one file, the attacker can know the URLs imported from that file

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.

PoC

Download reproduction.zip
Extract it and move to that directory
Run npm i
Run npm run watch
Run fetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.

Impact

Users using the serve feature may get the source code stolen by malicious websites.

Details about esbuild@0.2.10

Security Details

Comprehensive list of direct or transitive vulnerabilities for version 0.2.10 of the package esbuild.

All Security Vulnerabilities

All the vulnerabilities related to the version 0.2.10 of the package

Summary:

esbuild enables any website to send any requests to the development server and read the response

Details:

Summary

esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.

Details

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.

Attack scenario:

The attacker serves a malicious web page (http://malicious.example.com).
The user accesses the malicious web page.
The attacker sends a 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.
The attacker gets the content of 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

Fetching /index.html: normally you have a script tag here
Fetching /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
Connecting /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)))
Fetching URLs in the known file: once the attacker knows one file, the attacker can know the URLs imported from that file

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.

PoC

Download reproduction.zip
Extract it and move to that directory
Run npm i
Run npm run watch
Run fetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.

Impact

Users using the serve feature may get the source code stolen by malicious websites.

Details about esbuild@0.2.10

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.2.10 and 0.2.9

Version 0.2.10 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.2.10 and 0.2.9

Version 0.2.10 Details

Security Vulnerabilities

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

Summary

Details

PoC

Impact

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

Summary

Details

PoC

Impact

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.2.10 and 0.2.9

Version 0.2.10 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.2.10 and 0.2.9

Version 0.2.10 Details

Security Vulnerabilities

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

esbuild@0.2.10 GHSA-67mh-4wv8-2f99 5.3

Summary

Details

PoC

Impact

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

esbuild@0.2.10 GHSA-67mh-4wv8-2f99 5.3

Summary

Details

PoC

Impact