# CVE-2007-6200: Security feature bypass in n/a

> Remote attackers can bypass rsync daemon filters to read or write hidden files when the daemon is configured for writable access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6200, GHSA-2w9v-97wx-v5mj, RHSA-2011:0999

## What is CVE-2007-6200?

CVE-2007-6200 is a critical vulnerability in n/a, published on 1 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in rsync before 3.0.0pre6, when running a writable rsync daemon, allows remote attackers to bypass exclude, exclude_from, and filter and read or write hidden files via (1) symlink, (2) partial-dir, (3) backup-dir, and unspecified (4) dest options.

Weakness: CWE-264

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync` | Red Hat:enterprise_linux:5::client | All versions | 0:3.0.6-4.el5 |
| `rsync-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:3.0.6-4.el5 |
| `rsync` | Red Hat:enterprise_linux:5::server | All versions | 0:3.0.6-4.el5 |
| `rsync-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:3.0.6-4.el5 |

Products: Rsync Rsync.

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

Upgrade to a fixed version.

## Is CVE-2007-6200 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6199](https://insights.sbomify.com/CVE-2007-6199/): Path traversal in n/a (critical 9.3)
- [CVE-2007-4091](https://insights.sbomify.com/CVE-2007-4091/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6200 is a critical vulnerability in n/a, published on 1 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6200 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-2007-6200/ (Markdown: https://insights.sbomify.com/CVE-2007-6200/index.md)
```

## Sources

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

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