CVE-2026-2597

7.5

LEONT · Crypt::SysRandom::XS

Crypt::SysRandom::XS is vulnerable to a heap-based buffer overflow in the random_bytes function, which can lead to application crashes and denial of service.

Executive summary

A heap-based buffer overflow vulnerability in the Perl module Crypt::SysRandom::XS could allow an unauthenticated attacker to cause a denial of service via memory corruption.

Vulnerability

The vulnerability exists in the XS function random_bytes, which fails to validate that the length parameter is non-negative. An unauthenticated attacker providing a negative value can trigger an integer wraparound, resulting in heap memory corruption and potential application termination.

Business impact

The primary risk associated with this vulnerability is a denial of service, where an attacker can crash applications relying on this module for random number generation. While the CVSS score of 7.5 indicates high severity due to the potential for remote exploitation, the actual impact is limited to service availability rather than data exfiltration or unauthorized code execution in most standard implementations.

Remediation

Immediate Action: Update the Crypt::SysRandom::XS module to version 0.010 or later immediately to incorporate the necessary input validation checks.

Proactive Monitoring: Monitor application logs and system error reports for unexpected crashes or memory-related exceptions associated with the Perl runtime environment.

Compensating Controls: Ensure that any application passing user-controlled input to this module is strictly validating that all length parameters are positive integers before processing.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the potential for service disruption, administrators using the Crypt::SysRandom::XS module should prioritize upgrading to version 0.010. While the likelihood of successful exploitation depends on how the application handles input parameters, applying the vendor-provided patch is the only definitive way to eliminate the underlying heap overflow risk.

Sources