Js Compute
Approved changes feed: RSS · Atom
cpe:2.3:a:fastly:js-compute:*:*:*:*:*:node.js:*:*
part: a version: * update: *
| Vendor | Fastly (3e5a3d70-0766-5f43-88fe-235a49f661a2) |
|---|---|
| Product | Js Compute (f27569d6-1f0d-5479-8e8e-ffaa73dcb152) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-39218 |
vulnerable | 2026-06-08 05:47:18.365710 |
Random number seed fixed during compilation
HIGH (7.5)
The JS Compute Runtime for Fastly's Compute@Edge platform provides the environment JavaScript is executed in when using the Compute@Edge JavaScript SDK. In versions prior to 0.5.3, the `Math.random` and `crypto.getRandomValues` methods fail to use sufficiently random values. The initial value to seed the PRNG (pseudorandom number generator) is baked-in to the final WebAssembly module, making the sequence of random values for that specific WebAssembly module predictable. An attacker can use the fixed seed to predict random numbers generated by these functions and bypass cryptographic security controls, for example to disclose sensitive data encrypted by functions that use these generators. The problem has been patched in version 0.5.3. No known workarounds exist.
Published: 2022-09-20T19:50:08.000Z
Updated: 2025-04-23T16:56:59.041Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.