Persistent service crash via incomplete SOAP requests
Published Oct 22, 2025 · Updated Oct 22, 2025
Failure to handle incomplete elements in SAUTER building controllers allows remote attackers to crash wscserver with incomplete SOAP requests. SOAP request handling in wscserver fails to reject incomplete input safely and instead terminates the service process. No authentication or user interaction is required, and the watchdog does not restart wscserver, leaving it unavailable until device reboot.
Summary
What happened
Failure to handle incomplete elements in SAUTER building controllers allows remote attackers to crash wscserver with incomplete SOAP requests. SOAP request handling in wscserver fails to reject incomplete input safely and instead terminates the service process. No authentication or user interaction is required, and the watchdog does not restart wscserver, leaving it unavailable until device reboot.
The record
- CVE
- CVE-2025-41724
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- Fr. Sauter AG
- Product
- SAUTER EY-modulo 5 modu524
- Classifications
- CWE-239, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0 <Firmware v6.0
What conditions does exploitation require?
What is affected?
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