dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-64129

HIGH · 7.6 CVSS v3.1 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zenitel TCIV-3+ is vulnerable to an out-of-bounds write vulnerability, which could allow a remote attacker to crash the device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Zenitel TCIV-3+ intercom/video device contains an out-of-bounds write vulnerability that allows a remote attacker to write beyond allocated memory boundaries, causing the device to crash. The high CVSS score reflects the network-exploitable nature and availability impact of causing device unavailability.

MitigationApply vendor firmware update when available; otherwise, minimize attack surface by isolating the device behind a firewall and restricting network access to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Zenitel TCIV-3+
    Access the device web interface, check the device information page, or query the device via SNMP/manufacturer API to verify the exact model number.
    Affected if The device model is TCIV-3+ (any firmware version)
  2. Identify installed firmware version
    Locate the firmware version in the device web interface under 'System' or 'About' section, or use the manufacturer's management software to query the device.
    Affected if The firmware version is older than the vendor-fixed version (compare against release notes from Zenitel for this CVE)
  3. Verify network exposure of the device
    Check network firewall rules, ACLs, and device IP assignment to determine if the device is accessible from untrusted networks.
    Affected if The device management interface or video streaming ports are reachable from outside the trusted network segment
  4. Check for disabled or non-essential network services
    Review the device configuration to determine which network services (HTTP, HTTPS, RTSP, etc.) are enabled and whether they are necessary for operation.
    Affected if Unnecessary network services are enabled and exposed, increasing the attack surface for this network-exploitable flaw

The environment is affected if a Zenitel TCIV-3+ device is in use and the vendor firmware update addressing this out-of-bounds write vulnerability has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update when available; otherwise, minimize attack surface by isolating the device behind a firewall and restricting network access to trusted sources only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64129 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data