Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade github.com/gofiber/utils/v2 to version 1.2.0, 2.0.0-rc.4 or higher.
Affected versions of this package are vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) due to the UUIDv4 and UUID functions silently returning predictable values, such as the zero UUID, when the cryptographic random number generator fails. An attacker can compromise the integrity and confidentiality of security-sensitive identifiers by triggering or exploiting failures in the system's entropy source, leading to predictable session IDs, CSRF tokens, authentication tokens, and widespread identifier collisions across the application.
Note: Applications running on Go 1.24 or above are not vulnerable because Rand() panics rather than falling back to predictable UUID assignment.
This vulnerability can be mitigated by replacing usage of the affected functions with a secure alternative, such as using uuid.New() from a trusted library.