CVE-2025-34105
Published: 15 July 2025
Summary
CVE-2025-34105 is a critical-severity Improper Input Validation (CWE-20) vulnerability. Its CVSS base score is 10.0 (Critical).
Operationally, ranked in the top 1.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
A stack-based buffer overflow vulnerability exists in the built-in web interface of DiskBoss Enterprise versions 7.4.28, 7.5.12, and 8.2.14. The flaw stems from improper bounds checking on the path component of incoming HTTP GET requests and is tracked under CWE-20 and CWE-787. It carries a CVSS 4.0 score of 10.0, reflecting network-accessible, low-complexity conditions that require no authentication or user interaction.
A remote unauthenticated attacker can exploit the issue by sending a specially crafted long URI to the web interface. Successful exploitation can trigger arbitrary code execution with SYSTEM-level privileges on the underlying Windows host.
Public exploit code is available, including a Metasploit module and entries in Exploit-DB, while the current EPSS score of 0.6655 indicates substantial exploitation interest. No official patch or mitigation details are provided in the referenced sources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21434
Vulnerability details
A stack-based buffer overflow vulnerability exists in the built-in web interface of DiskBoss Enterprise versions 7.4.28, 7.5.12, and 8.2.14. The vulnerability arises from improper bounds checking on the path component of HTTP GET requests. By sending a specially crafted long…
more
URI, a remote unauthenticated attacker can trigger a buffer overflow, potentially leading to arbitrary code execution with SYSTEM privileges on vulnerable Windows hosts.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.