# CVE-2009-4606: Privilege escalation in n/a

> Local attackers can escalate privileges to SYSTEM by exploiting insecure service permissions in the WebDrive client installation.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9mq4-39cv-h79m

## What is CVE-2009-4606?

CVE-2009-4606 is a high-severity vulnerability in n/a, published on 13 Jan 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

South 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.

Weakness: CWE-264

## Which versions are affected by CVE-2009-4606?

It affects 1 product.


Products: South River Technologies Webdrive.

## How do I fix CVE-2009-4606?

No fix has been published for CVE-2009-4606 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-4606 being exploited?

There is no known exploitation of CVE-2009-4606 in the wild and no public exploit code.

Public exploit code:

- South River Technologies WebDrive Service 9.02 build 2232 - Bad Security Descriptor Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4606 and fix it if it is affected.

What it is: CVE-2009-4606 is a high-severity vulnerability in n/a, published on 13 Jan 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4606 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-4606/ (Markdown: https://insights.sbomify.com/CVE-2009-4606/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-4606
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-4606
- OSV: https://osv.dev/vulnerability/CVE-2009-4606

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-4606/
Summaries are generated and may contain mistakes; the official description above is the record.