@fastly/js-compute
Affected
- introduced
3.0.0, fixed3.16.0(semver)
Fixed versions
3.16.0
Fix
- Fixed version
3.16.0npm install @fastly/[email protected]
Advisory
Also known as: CVE-2024-38375
@fastly/js-compute has a use-after-free in some host call implementations
Impact
The implementation of the following functions were determined to include a use-after-free bug:
FetchEvent.client.tlsCipherOpensslNameFetchEvent.client.tlsProtocolFetchEvent.client.tlsClientCertificateFetchEvent.client.tlsJA3MD5FetchEvent.client.tlsClientHelloCacheEntry.prototype.userMetadata of the fastly:cache subsystemDevice.lookup of the fastly:device subsystemThis bug could allow for an unintended data leak if the result of the preceding functions were sent anywhere else, and often results in a Compute service crash causing an HTTP 500 error to be returned. As all requests to Compute are isolated from one another, the only data at risk is data present for a single request.
Patches
This bug has been fixed in version 3.16.0 of the @fastly/js-compute package.
Workarounds
There are no workarounds for this bug, any use of the affected functions introduces the possibility of a data leak or crash in guest code.
Medium Basis: The source's own band: MODERATE
3.0.0, fixed 3.16.0 (semver)3.16.0
3.16.0npm install @fastly/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0