LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-3194 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:Psnyk
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P3.93.6snyk

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2025-3194Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/abigint-buffer0.0.0Listed
Weakness

CWE details

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.