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.
This bug has been fixed in version 3.16.0 of the @fastly/js-compute package.
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.
{
"severity": "MODERATE",
"github_reviewed_at": "2024-06-26T19:12:23Z",
"cwe_ids": [
"CWE-416"
],
"nvd_published_at": "2024-06-26T19:15:13Z",
"github_reviewed": true
}