What is GHSA-mp3g-vpm9-9vqv?

GHSA-mp3g-vpm9-9vqv is a security advisory published by GitHub Security Advisories with Medium severity. @fastly/js-compute has a use-after-free in some host call implementations

Which CVE IDs does GHSA-mp3g-vpm9-9vqv cover?

GHSA-mp3g-vpm9-9vqv covers the following CVE IDs: CVE-2024-38375. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-mp3g-vpm9-9vqv?

GHSA-mp3g-vpm9-9vqv has a CVSS v3 base score of 5.3, published by GitHub Security Advisories.

Which products are affected by GHSA-mp3g-vpm9-9vqv?

GHSA-mp3g-vpm9-9vqv affects 1 product, including: npm/@fastly/js-compute:\u003e= 3.0.0, \u003c 3.16.0.

GHSA-mp3g-vpm9-9vqvMediumCVSS 5.3

@fastly/js-compute has a use-after-free in some host call implementations

Vendor

GitHub Security Advisories

Published

June 26, 2024

Last Modified

June 26, 2024

🔗 CVE IDs covered (1)

CVE-2024-38375 →

📋 Description

Impact

The implementation of the following functions were determined to include a use-after-free bug:

FetchEvent.client.tlsCipherOpensslName
FetchEvent.client.tlsProtocol
FetchEvent.client.tlsClientCertificate
FetchEvent.client.tlsJA3MD5
FetchEvent.client.tlsClientHello
CacheEntry.prototype.userMetadata of the fastly:cache subsystem
Device.lookup of the fastly:device subsystem

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

🎯 Affected products1

npm/@fastly/js-compute:>= 3.0.0, < 3.16.0