CVE-2022-39218: Random number seed fixed during compilation
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-39218?
CVE-2022-39218 is classified as having high severity due to the inadequate randomness in the `Math.random` and `crypto.getRandomValues` methods.
How do I fix CVE-2022-39218?
To fix CVE-2022-39218, upgrade the Fastly JS Compute Runtime to version 0.5.3 or higher.
What impact does CVE-2022-39218 have on security?
CVE-2022-39218 can lead to predictable randomness in cryptographic operations, making it easier for attackers to exploit applications.
Which versions of Fastly's JS Compute Runtime are affected by CVE-2022-39218?
Versions of Fastly's JS Compute Runtime prior to 0.5.3 are affected by CVE-2022-39218.
Is there a workaround for CVE-2022-39218?
There is no official workaround for CVE-2022-39218; upgrading to the patched version is the recommended action.