Version Details and Security Vulnerabilities

📦

esbuild

0.7.7

Comparision Betweeen 0.7.7 and 0.7.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

37.26 KB

Version 0.7.7 Details

Esbuild versions 0.7.6 and 0.7.7 are incremental releases of this extremely fast JavaScript bundler and minifier, both licensed under the MIT license. Both versions share the same core characteristics: they bundle and minify JavaScript code with exceptional speed, making them a valuable asset for developers seeking to optimize build times. The repository URL, git+https://github.com/evanw/esbuild.git, remains consistent across both versions, indicating that the source code is managed in the same GitHub repository.

Both distributions have a fileCount of 6 and an unpackedSize of 38150 bytes, this suggests that the changes between the releases might be related to internal fixes, performance enhancements, or minor feature tweaks rather than significant structural alterations to the package. The primary distinction lies in their release dates. Version 0.7.6 was released on September 26, 2020, while version 0.7.7 followed shortly after, on September 27, 2020.

For developers, this rapid succession of releases suggests a focus on actively maintaining and improving esbuild. If you're already using esbuild, upgrading from 0.7.6 to 0.7.7 is likely a safe move to benefit from the latest bug fixes and potential optimizations. While the changes might not be drastic, staying current with minor version updates demonstrates a commitment to stability and performance. These packages are great for front-end developers, full-stack developers, and anyone who wants to improve the build speed.

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

Comparision Betweeen 0.7.7 and 0.7.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

37.26 KB

Version 0.7.7 Details

Security Vulnerabilities

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.7.7 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.7.7

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.7.7 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.7.7

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.7.7 and 0.7.6

Version 0.7.7 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.7.7 and 0.7.6

Version 0.7.7 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.7.7 and 0.7.6

Version 0.7.7 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.7.7 and 0.7.6

Version 0.7.7 Details

Security Vulnerabilities

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact