CVE-2025-3194: Versions of the package bigint-buffer from 0.0.0 are vulnerable to Buffer Overflow in the toBigIntLE() func...
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-3194 affects the JavaScript package bigint-buffer. A buffer overflow in toBigIntLE() can let an attacker crash an application. The business impact is mainly availability: services using this package on attacker-controlled data may be vulnerable to denial of service.
Executive priority
Treat as a high-priority availability risk for internet-facing or API-driven services using bigint-buffer. Prioritize inventory and reachability first, because supplied sources do not name a fixed version or confirm active exploitation.
Technical view
The source bundle describes CWE-120 in bigint-buffer versions from 0.0.0, specifically toBigIntLE(). CVSS v4.0 is 8.7 with network attack vector, low complexity, no privileges, no user interaction, and high vulnerable-system availability impact. No confidentiality or integrity impact is indicated.
Likely exposure
Exposure is most likely in Node.js applications that include bigint-buffer and pass untrusted or remotely supplied buffers into toBigIntLE(). Confirm through dependency manifests, lockfiles, SBOMs, and runtime reachability.
Exploitation context
The CVSS vector indicates remote, unauthenticated, low-complexity exploitation with no user interaction. The CVE is not listed as KEV in the supplied data, and no cited source shows active exploitation. Impact described is application crash.
Researcher notes
Evidence is limited to the CVE/Snyk description, code reference, and related research paper. The supplied bundle does not provide a patch commit, fixed release, or exploitation-in-the-wild evidence. Focus validation on dependency presence and whether attacker-controlled data reaches toBigIntLE().
Mitigation direction
Identify all applications depending on bigint-buffer.
Check Snyk, CVE, npm, and maintainer guidance for fixed versions.
Upgrade, replace, or remove the package when vendor guidance supports it.
Avoid passing untrusted input to toBigIntLE() where feasible.
Add input validation and graceful error handling around affected parsing paths.
Validation and detection
Search package.json, lockfiles, and SBOMs for bigint-buffer.
Confirm deployed versions across build and runtime environments.
Determine whether toBigIntLE() is reachable from remote inputs.
Run software composition analysis using current vulnerability data.
Verify remediation through dependency rescan and regression testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.