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

> Authenticated users can bypass scponly restrictions to execute arbitrary code via dangerous subcommands like svn or rsync.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/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:** 14 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5f6x-8rc3-r4j2

## What is CVE-2007-6350?

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

### Official description

scponly 4.6 and earlier allows remote authenticated users to bypass intended restrictions and execute code by invoking dangerous subcommands including (1) unison, (2) rsync, (3) svn, and (4) svnserve, as originally demonstrated by creating a Subversion (SVN) repository with malicious hooks, then using svn to trigger execution of those hooks.

Weakness: CWE-264

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

It affects 1 product.


Products: Scponly Scponly.

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

Upgrade to a fixed version.

## Is CVE-2007-6350 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4533](https://insights.sbomify.com/CVE-2005-4533/): Command injection in n/a (high 7.5)
- [CVE-2002-1469](https://insights.sbomify.com/CVE-2002-1469/): Path traversal in n/a (high 7.5)
- [CVE-2005-4532](https://insights.sbomify.com/CVE-2005-4532/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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