Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12917: Denial of Service in TOZED ZLT T10

0
Medium
VulnerabilityCVE-2025-12917cvecve-2025-12917
Published: Sun Nov 09 2025 (11/09/2025, 07:32:06 UTC)
Source: CVE Database V5
Vendor/Project: TOZED
Product: ZLT T10

Description

A vulnerability was identified in TOZED ZLT T10 T10PLUS_3.04.15. The affected element is an unknown function of the file /reqproc/proc_post of the component Reboot Handler. Such manipulation leads to denial of service. Access to the local network is required for this attack to succeed. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 11/16/2025, 08:40:59 UTC

Technical Analysis

CVE-2025-12917 identifies a denial of service vulnerability in the TOZED ZLT T10 device, specifically in firmware version T10PLUS_3.04.15. The vulnerability resides in an unspecified function within the /reqproc/proc_post file, part of the Reboot Handler component. The Reboot Handler likely manages device reboot processes or recovery operations. By sending crafted requests over the local network, an attacker can manipulate this function to cause a denial of service, rendering the device unresponsive or forcing a reboot loop. The attack vector requires local network access, meaning the attacker must be within the same network segment or have compromised network access. No authentication or user interaction is required, which lowers the barrier for exploitation once local access is obtained. The CVSS 4.0 base score is 5.3 (medium), reflecting limited impact on confidentiality and integrity but a clear impact on availability. The exploit code is publicly available, increasing the risk of exploitation, although no active exploitation has been reported. The vendor has not issued any patches or advisories, and no mitigation guidance is provided by them. This lack of vendor response increases the urgency for organizations to implement compensating controls. The vulnerability affects only the specified firmware version, so devices running other versions may not be vulnerable. However, without vendor updates, it is unclear if newer versions address this issue. The vulnerability’s presence in a network device used potentially in industrial or enterprise environments could disrupt network operations and availability of services relying on these devices.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the availability of network infrastructure where TOZED ZLT T10 devices are deployed. Disruption of these devices could lead to network outages, impacting business continuity, especially in sectors relying on stable network operations such as manufacturing, utilities, and critical infrastructure. The requirement for local network access limits remote exploitation but does not eliminate risk from insider threats or lateral movement by attackers who have breached perimeter defenses. The lack of vendor response and patches means organizations must rely on network-level mitigations and monitoring. In environments with high deployment of these devices, the impact could be significant, causing operational downtime and potential financial losses. Additionally, disruption of network devices could indirectly affect confidentiality and integrity if fallback mechanisms or failover systems are not properly configured. The public availability of exploit code increases the likelihood of opportunistic attacks, especially in less secure local networks.

Mitigation Recommendations

Given the absence of vendor patches, European organizations should implement the following specific mitigations: 1) Segment networks to isolate TOZED ZLT T10 devices from general user access and untrusted devices, minimizing local network exposure. 2) Employ strict access controls and network monitoring to detect anomalous traffic targeting the /reqproc/proc_post endpoint or unusual reboot patterns. 3) Use network intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to identify exploitation attempts based on the public exploit characteristics. 4) Regularly audit device firmware versions and configurations to identify and isolate vulnerable devices. 5) Where possible, replace or upgrade devices to versions not affected by this vulnerability or alternative products with vendor support. 6) Implement robust internal network security policies to prevent lateral movement and restrict access to critical network devices. 7) Maintain incident response readiness to quickly address any denial of service incidents involving these devices. 8) Engage with TOZED or authorized vendors for updates or support, and monitor for any future patches or advisories.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-08T16:44:29.640Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6910457ac786195411069ca1

Added to database: 11/9/2025, 7:40:42 AM

Last enriched: 11/16/2025, 8:40:59 AM

Last updated: 12/23/2025, 9:43:14 AM

Views: 84

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats