Device reboot via mishandled PROCOME TLS requests
Published Jun 6, 2025 · Updated Jun 6, 2025
Uncontrolled resource consumption in ZIV IDF 0.10.0-0C03-03 and ZLF 0.10.0-0C03-04 allows remote attackers to reboot devices. The PROCOME socket TLS path improperly handles incoming requests, causing the affected protection device to reboot. Exploitation requires configured and active PROCOME ports with communications encryption enabled, and the resulting interruption is a device reboot.
Summary
What happened
Uncontrolled resource consumption in ZIV IDF 0.10.0-0C03-03 and ZLF 0.10.0-0C03-04 allows remote attackers to reboot devices. The PROCOME socket TLS path improperly handles incoming requests, causing the affected protection device to reboot. Exploitation requires configured and active PROCOME ports with communications encryption enabled, and the resulting interruption is a device reboot.
The record
- CVE
- CVE-2025-41361
- Published
- Jun 6, 2025
- Updated
- Jun 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Jun 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo