dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-34105

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
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 URI, a remote unauthenticated attacker can trigger a buffer overflow, potentially leading to arbitrary code execution with SYSTEM privileges on vulnerable Windows hosts.

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 · high confidence

A stack-based buffer overflow exists in DiskBoss Enterprise's built-in web interface due to improper bounds checking on the path component of HTTP GET requests. An attacker can send an excessively long URI to trigger the overflow and execute arbitrary code with SYSTEM privileges on vulnerable Windows hosts.

MitigationApply vendor patches for versions 7.4.28, 7.5.12, and 8.2.14 when released. As an interim control, restrict or disable the built-in web interface and implement network segmentation to limit exposure to unauthenticated attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DiskBoss Enterprise installation
    Look for DiskBoss Enterprise in the list of installed programs via Windows Control Panel > Programs and Features, or check for the installation directory (commonly C:\Program Files\DiskBoss Enterprise or C:\Program Files (x86)\DiskBoss Enterprise)
    Affected if DiskBoss Enterprise is installed on the system
  2. Identify installed DiskBoss version
    Locate the version information in the installation folder, typically in a file named version.txt, or right-click on the main executable and select Properties > Details to view the File Version
    Affected if The installed version is below 7.4.28, 7.5.12, or 8.2.14 (compare your version to these thresholds)
  3. Determine if web interface is enabled
    Check the DiskBoss service configuration or look for a running process named diskboss.exe or diskbotsrv.exe listening on HTTP ports (default web interface ports are 80 and 8080). Use command: netstat -an | findstr "LISTENING" and look for ports 80, 8080, or configured custom ports
    Affected if The built-in web interface is actively running and listening on a network port
  4. Verify web interface is network-accessible
    Confirm the web interface is bound to a network-advertised IP rather than localhost only. Check the DiskBoss server configuration file (usually diskboss.xml or diskbosssrv.xml in the config folder) for the ListenAddress or BindAddress setting
    Affected if The web interface is bound to 0.0.0.0 or a routable IP address, making it accessible from the network

A user is affected if DiskBoss Enterprise is installed with a version prior to 7.4.28, 7.5.12, or 8.2.14 AND the built-in web interface is running and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for versions 7.4.28, 7.5.12, and 8.2.14 when released. As an interim control, restrict or disable the built-in web interface and implement network segmentation to limit exposure to unauthenticated attackers.

Recommended fix Moderate confidence

Contact vendor for latest patched version (newer than 8.2.14)

  1. 1. Verify the exact version of DiskBoss Enterprise installed by checking the application or service properties.
  2. 2. Contact FlexQuest (DiskBoss vendor) directly to request the latest patched version and inquire about CVE-2025-34105 fixes.
  3. 3. As a temporary mitigation, restrict network access to the DiskBoss web interface to trusted IP addresses only using firewall rules or network ACLs.
  4. 4. If the web interface is not required for external operations, disable it or bind it to localhost only.
  5. 5. Monitor vendor security advisories for upcoming patches and apply them immediately upon release.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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