CVE-2009-4606
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 · uneditedSouth River Technologies WebDrive 9.02 build 2232 installs the WebDrive Service without a security descriptor, which allows local users to (1) stop the service via the stop command, (2) execute arbitrary commands as SYSTEM by using the config command to modify the binPath variable, or (3) restart the service via the start command.
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 confidenceSouth River Technologies WebDrive 9.02 installs its Windows service without a security descriptor, allowing any local user to start, stop, or reconfigure the service. Attackers can modify the binPath to point to malicious executables and achieve SYSTEM-level code execution.
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= 9.02CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Check if WebDrive service is installedOpen Services console (services.msc) or run 'sc query WebDrive' from command prompt to see if the WebDrive service existsAffected if The WebDrive service is present on the system
-
Identify installed WebDrive versionCheck the version of WebDrive.exe in the installation directory (commonly C:\Program Files\South River Technologies\WebDrive\ or C:\Program Files (x86)\South River Technologies\WebDrive\) or check the file properties of WebDrive.exeAffected if The installed version is exactly 9.02 (the affected version)
-
Verify service security descriptor is missing or weakRun 'sc sdshow WebDrive' from an elevated command prompt to display the service's Security Descriptor Definition Language (SDDL). Check if the DACL (Discretionary Access Control List) section is empty, missing, or contains 'Everyone', 'Users', or 'Authenticated Users' with service control permissionsAffected if The security descriptor is empty, missing, or grants write access to non-Administrators (such as Everyone, Users, or Authenticated Users)
-
Confirm service can be modified by non-admin usersAttempt to change the service binary path using 'sc config WebDrive binPath= "C:\test.exe"' from a non-elevated command prompt running as a standard user accountAffected if A standard user can successfully modify the service configuration without administrator privileges
A system is affected if WebDrive version 9.02 is installed and its Windows service lacks a proper security descriptor, allowing any local user to modify the service configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataApply a proper security descriptor to the WebDrive service using Windows sc.exe sdset command or equivalent, restricting service control to Administrators only. Alternatively, upgrade to a patched version of WebDrive if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-4606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-4606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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