# CVE-2007-4006: Memory corruption in n/a

> A buffer overflow in the Windows RSH daemon allows remote attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qq35-r26p-ch7c

## What is CVE-2007-4006?

CVE-2007-4006 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2007. It can be exploited over the network, with no action from the victim.

### Official description

Buffer overflow in Mike Dubman Windows RSH daemon (rshd) 1.7 has unknown impact and remote attack vectors, aka ZD-00000034.  NOTE: this information is based upon a vague advisory by a vulnerability information sales organization that does not coordinate with vendors or release actionable advisories. A CVE has been assigned for tracking purposes, but duplicates with other CVEs are difficult to determine.

## Which versions are affected by CVE-2007-4006?

It affects 1 product.


Products: Mike Dubman Windows Rsh Daemon.

## How do I fix CVE-2007-4006?

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

## Is CVE-2007-4006 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4006 exists.

Public exploit code:

- Microsoft Windows RSH daemon 1.7 - Remote Buffer Overflow (exploitdb)
- Windows RSH Daemon Buffer Overflow (metasploit)
- Microsoft Windows RSH daemon - Remote Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4005](https://insights.sbomify.com/CVE-2007-4005/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4006 and fix it if it is affected.

What it is: CVE-2007-4006 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2007. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4006 exists.

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-2007-4006/ (Markdown: https://insights.sbomify.com/CVE-2007-4006/index.md)
```

## Sources

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

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