bigint-buffer toBigIntLE buffer overflow

Summaryinfo

A vulnerability identified as critical has been detected in bigint-buffer. This affects the function toBigIntLE. The manipulation leads to buffer overflow. This vulnerability is referenced as CVE-2025-3194. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in bigint-buffer (affected version not known) and classified as critical. This issue affects the function toBigIntLE. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is availability. The summary by CVE is:

Versions of the package bigint-buffer from 0.0.0 are vulnerable to Buffer Overflow in the toBigIntLE() function. Attackers can exploit this to crash the application.

The advisory is shared at security.snyk.io. The identification of this vulnerability is CVE-2025-3194 since 04/03/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/04/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• bigint-buffer

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion