dbcve.org
WebdriveApplication · South River

CVE-2006-0867

MEDIUM · 5.0 CVSS v2.0 Published 2006-02-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Buffer overflow in certain versions of South River (aka SRT) WebDrive, possibly version 6.08 build 1131 and version 8, allows remote attackers to cause a denial of service (application crash and persistent erratic behavior) via a long string in the name entry field.

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

Buffer overflow vulnerability in South River WebDrive allows remote attackers to cause denial of service via a long string in the name entry field, leading to application crash and persistent erratic behavior. Affected versions include possibly version 6.08 build 1131 and version 8.

MitigationUpgrade WebDrive to a patched version beyond 6.08/8, or contact the vendor (now Corel) for an updated, secure release.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebdriveApplication
Affected:= 6.08_build_1131= 8

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 WebDrive installation
    Check Add/Remove Programs for South River WebDrive, or search for WebDrive.exe in Program Files directories
    Affected if WebDrive is present on the system
  2. Identify installed version number
    Right-click WebDrive.exe, select Properties, and check the Version tab; alternatively use Help > About in the application menu
    Affected if Version displays as 6.08_build_1131 or version 8.x
  3. Check version in Windows registry
    Examine registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{WebDrive GUID} or look for version strings under HKLM\SOFTWARE\South River Technologies
    Affected if Registry version entry matches 6.08_build_1131 or 8.x
  4. Verify exact build number
    If version shows 6.08 or 8.0, right-click the executable, select Properties, and check the Details tab for Product Version to confirm the specific build
    Affected if Build number matches 6.08_build_1131 or falls within version 8.x

The environment is affected if South River WebDrive version 6.08_build_1131 or version 8 is installed on the system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WebDrive to a patched version beyond 6.08/8, or contact the vendor (now Corel) for an updated, secure release.

Fix this in Webdrive Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-0867 — 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-2006-0867 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