# CVE-2004-2730: Privilege escalation in n/a

> Local users can access remote IPC$ and ADMIN$ shares with elevated privileges due to improper disconnection in PsTools utilities.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 9 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-679x-cxhr-6g88

## What is CVE-2004-2730?

CVE-2004-2730 is a medium-severity vulnerability in n/a, published on 9 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sysinternals PsTools before 2.05, including (1) PsExec before 1.54, (2) PsGetsid before 1.41, (3) PsInfo before 1.61, (4) PsKill before 1.03, (5) PsList before 1.26, (6) PsLoglist before 2.51, (7) PsPasswd before 1.21, (8) PsService before 2.12, (9) PsSuspend before 1.05, and (10) PsShutdown before 2.32, does not properly disconnect from remote IPC$ and ADMIN$ shares, which allows local users to access the shares with elevated privileges by using the existing share mapping.

Weakness: CWE-264

## Which versions are affected by CVE-2004-2730?

It affects 11 products.


Products: Microsoft Psexec, Microsoft Psgetsid, Microsoft Psinfo, Microsoft Pskill, Microsoft Pslist, Microsoft Psloglist, Microsoft Pspasswd, Microsoft Psservice, Microsoft Psshutdown, Microsoft Pssuspend, Microsoft Sysinternals Pstools.

## How do I fix CVE-2004-2730?

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

## Is CVE-2004-2730 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-1733](https://insights.sbomify.com/CVE-2021-1733/): Sysinternals PsExec Elevation of Privilege Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2730 and fix it if it is affected.

What it is: CVE-2004-2730 is a medium-severity vulnerability in n/a, published on 9 Oct 2007. 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-2004-2730 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-2004-2730/ (Markdown: https://insights.sbomify.com/CVE-2004-2730/index.md)
```

## Sources

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

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