Version Details and Security Vulnerabilities

📦

esbuild

0.5.3

Comparision Betweeen 0.5.3 and 0.5.2

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.86 KB

Version 0.5.3 Details

Esbuild is a blazing-fast JavaScript bundler and minifier, designed to significantly improve build times for web development projects. Version 0.5.3, released shortly after version 0.5.2, continues to build upon this foundation of speed and efficiency. While both versions share the same core functionality, description, MIT license, repository details pointing to the official GitHub, identical fileCount of 6 and unpackedSize of 19309 bytes in their distributed packages, the key difference lies in their release timestamps. Version 0.5.3 arrived on June 12, 2020, at 05:33:43.540Z, a mere four and a half hours after version 0.5.2, which was released at 01:02:14.932Z on the same day.

This relatively short time between releases suggests that version 0.5.3 likely contains minor bug fixes, potentially addressing issues discovered in version 0.5.2 shortly after its initial deployment, or very small enhancements. Developers already using esbuild should consider upgrading to version 0.5.3 to benefit from these immediate improvements and ensure they are running the most stable and up-to-date iteration. For new users, starting with version 0.5.3 is recommended to leverage the latest refinements offered by this powerful tool. While the specific fixes or enhancements are not explicitly detailed in the provided metadata, the rapid release cycle indicates a commitment to quick issue resolution and continuous improvement by the esbuild team, making it a reliable choice for performance-conscious developers.

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.5.3

Comparision Betweeen 0.5.3 and 0.5.2

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.86 KB

Version 0.5.3 Details

Security Vulnerabilities

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.5.3 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.5.3

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.5.3 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.5.3

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.5.3 and 0.5.2

Version 0.5.3 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.5.3 and 0.5.2

Version 0.5.3 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.5.3 and 0.5.2

Version 0.5.3 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.5.3 and 0.5.2

Version 0.5.3 Details

Security Vulnerabilities

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact