Version Details and Security Vulnerabilities

📦

esbuild

0.15.9

Comparision Betweeen 0.15.9 and 0.15.8

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

117.66 KB

114.82 KB

Version 0.15.9 Details

Esbuild version 0.15.9 is a minor update to the blazingly fast JavaScript and CSS bundler and minifier, building upon the foundation laid by version 0.15.8. Both versions share the same core description and MIT license, emphasizing their commitment to speed and developer-friendly licensing. The primary difference lies in the versions of their platform-specific dependencies. Both versions bundle executables for various operating systems and architectures (Linux, macOS, Windows, Android, FreeBSD, NetBSD, OpenBSD, SunOS), ensuring broad compatibility.

The significance for developers considering an upgrade resides in dependency updates. While the functionality of esbuild itself remains consistent, version 0.15.9 pulls in the 0.15.9 versions of platform-specific binaries like esbuild-linux-64, esbuild-darwin-arm64, @esbuild/android-arm and all the others. This likely incorporates bug fixes and performance improvements within those individual builds. Developers should upgrade if they are experiencing platform-specific issues that may have been addressed. The change in unpacked size (120481 vs 117577) indicates potentially larger binaries, but also improved features/fixes in the new release. The release dates suggest a proactive development cycle prioritizing continuous enhancements. It's recommended to review the changelogs associated with the individual platform binaries if meticulous platform-specific stability are critical to your software.

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

Comparision Betweeen 0.15.9 and 0.15.8

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

117.66 KB

114.82 KB

Version 0.15.9 Details

Security Vulnerabilities

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.15.9 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.15.9

Security Details

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

All Security Vulnerabilities

All the vulnerabilities related to the version 0.15.9 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.15.9

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.15.9 and 0.15.8

Version 0.15.9 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.15.9 and 0.15.8

Version 0.15.9 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.15.9 and 0.15.8

Version 0.15.9 Details

Security Vulnerabilities

Version Details and Security Vulnerabilities

esbuild

Comparision Betweeen 0.15.9 and 0.15.8

Version 0.15.9 Details

Security Vulnerabilities

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact

Security Details

All

Transitive Dependencies

Package

All Security Vulnerabilities

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

Summary

Details

PoC

Impact