CVE-2025-64091
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 · uneditedThis vulnerability allows authenticated attackers to execute commands via the NTP-configuration of 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 confidenceThis is a command injection vulnerability in the NTP configuration functionality of a network device. An attacker with valid credentials can inject and execute arbitrary OS commands through improperly sanitized NTP configuration parameters, potentially achieving full device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.2.3.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware versionAccess the device administrative interface or check system information pages to retrieve the current firmware version. This is typically found under System, Status, or About sections in the web management console.Affected if The installed firmware version is any version of Zenitel Tcis 3 Firmware prior to 9.2.3.3 (for example, 9.2.3.2, 9.2.2.x, or earlier)
-
Locate NTP configuration settingsNavigate to the device configuration menus and find the NTP or time synchronization settings. These are commonly located under System Configuration, Network Settings, or Time settings in the web interface.Affected if NTP configuration functionality exists and is accessible on the device, as this is the vulnerable component
-
Verify administrative access methodConfirm how the device administrative interface is accessed (HTTP/HTTPS, port number, and network interface binding). Check if remote administrative access is enabled and which IP ranges can reach it.Affected if The administrative interface is accessible from untrusted networks, as the attacker needs valid credentials to exploit the command injection
You are affected if your Zenitel Tcis 3 device runs firmware version earlier than 9.2.3.3 AND has NTP configuration accessible to users with administrative credentials.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped9.2.3.3
Apply vendor-provided patches when available; if no patch exists, implement network access controls to limit administrative interface exposure and consider disabling NTP configuration via unauthenticated channels if supported.
TCIS 3 Firmware version 9.2.3.3 or later
- Identify all TCIS 3 devices on the network requiring remediation
- Check the current firmware version of each device (via web interface or CLI)
- Download firmware version 9.2.3.3 or later from the official Zenitel support portal
- Follow Zenitel's standard firmware upgrade procedure to apply the update to each affected device
- Verify the firmware was successfully applied and the device is operational
- Confirm the NTP configuration functionality is working correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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